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.
En esta sesión vamos a crear un blog desde cero con Microsoft Azure. Nuestro blog admitirá comentarios y valoraciones de cada entrada. Para ello, vamos a utilizar ASP.NET MVC en la parte cliente, y colas, WebJobs, DocumentDB y Application Insights en la parte cloud. Veremos como crear cada una de las partes que forman parte de la aplicación, y algunos consejos y recomendaciones a la hora de trabajar con algunas de estas tecnologías.
Microsoft Office and SharePoint Server 2013 introduce a new app model that brings the best of web development to Office and SharePoint. This session shows you how to get started and quickly create apps on this new model with the browser based tooling codenamed “Napa”, and how you can turn those apps into more advanced, rich scenarios with Visual Studio 2013.
In this episode you'll get to explore the cross-platform mobile strategy we took with the project, and how we built our app using Apache Cordova framework, just once, with it working on any device a volunteer would want to use. We also dive deeper into how Visual Studio 2015 enabled us to build this app quickly and easily, along with how we took advantage of our own (free) Android emulator and other cool debugging experiences.
We'll end the episode with a tour of the mobile app we made over the 3-day event, with all source code available now on GitHub: https://github.com/htbox/