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.
Organizational customers want consistent identities and access control across Active Directory (AD) and the software-as-a-service apps they rely upon, including Microsoft Office 365, salesforce.com, Box, WebEx, GoToMeeting, Concur, etc. This session covers how customers can enable Azure AD for SSO to hundreds of popular SaaS apps, along with configuring provisioning, federation, and password vaulting, and how to address the typical rollout concerns for enterprise-wide deployment of SaaS single sign-on.
Join this session for a journey through the lifecycle of a Microsoft Application Virtualization (App-V) 5.0 package. From the birth of a sequenced package through deployment, streaming, configuration, updates, connection groups, user customization and eventual termination. This session is based solely on stand-alone mode, demo-driven, behind-the-scenes views of how each part of the application lifecycle is handled by the App-V Client. No ties to Configuration Manager or Full Infrastructure, just an under the hood insight into how App-V applications are handled regardless of delivery mechanisms.