Apps should be tested before submission. Every app is unique, so a unique test plan should be created to test the components of each app. When creating the test plan, a few factors should be taken into account: app modules; how those modules interact within the app and in which order they are initialized; and which modules are required for the app to run. Based on this info, the modules should be tested. In this session, Mickey talks about how, through testing, you can ensure the highest quality for your app.
Even though you're watching this on-demand, Mickey wants to help. Post your questions, comments, etc below or tweet it, mentioning @cdndevs.
We'll award prizes to the first, second, and third place teams in the Games, Innovation, and World Citizenship categories. And then the three first-place teams will compete live onstage to see who takes home the overall Imagine Cup trophy and gets a private meeting with Bill Gates.
We've rewritten (and open sourced!) the C# and VB compilers, and exposed their functionality through APIs as the .NET Compiler Platform. But what do these APIs mean for those who aren't compiler jocks?
Learn about diagnostic analyzers, a key new feature of Visual Studio 2015 that lets a NuGet package introduce custom warnings and errors to your build. Analyzers let a NuGet package easily introduce custom warnings and errors to your build, along with automatic fixes in the IDE. We'll walk through the thought process and development of a simple diagnostic and code fix for the Regex API to see what it's like to quickly build analyzers for an API.