Do you want to create automated tests for your Windows Phone apps? With Microsoft Visual Studio 2013 Update 2 you can now create automated tests for your XAML-based Windows Phone apps. Starting from unit tests to functional end-to-end scenario tests, you can now perform all of your testing from the integrated Test Explorer in Visual Studio. These tests are seamlessly integrated with the automated build capabilities of Team Foundation Server. You now have the tools to build a gated check-in workflow or a continuous integration system easily. The testing framework is extensible and developers can customize it to meet the specialized needs of their application. In this session, we show you how to build comprehensive test suites for your Windows Phone apps by leveraging these Visual Studio capabilities, set up systems to prevent regressions, and overall ship a great quality app.
We are going to examine a variety of oopsies MANY developers fall prey too - some obvious, some pretty subtle and some down right sneaky! Lots of code examples with the bad AND good code presented. I GUARANTEE that you will find things here that will either prevent you from getting bad data, throwing unwanted errors or vastly improving your database application's performance. I have given this talk over SEVENTY times now and it is always very highly rated!
The standard library containers are often both misused and underused. Instead of creating new containers, applications are often structured with incidental data structures composed of objects referencing other object. This talk looks at some of the ways the standard containers can be better utilized and how creating (or using non-standard library) containers can greatly simplify code. The goal is no incidental data structures. -- Sean Parent is a principal scientist and software architect for Adobe's mobile digital imaging group. Sean has been at Adobe since 1993 when he joined as a senior engineer working on Photoshop and later managed Adobe's Software Technology Lab. In 2009 Sean spent a year at Google working on Chrome OS before returning to Adobe. From 1988 through 1993 Sean worked at Apple, where he was part of the system software team that developed the technologies allowing Apple's successful transition to PowerPC.