Testability is more important than ever. With short ship cycles and the desire for continuous delivery, it is critical to quickly know if a modification has destabilized your code base. This session will enable you to use a dependency injection container of your choice to create testable code. We will examine tightly coupled code and what problems it causes and how DI can be used to avoid these problems. The Unity DI container will be used as the medium to understand the concepts.
Join us for a deep dive into the troubleshooting tools available to Lync voice deployment engineers and administrators. We will dig into the logs and network captures. We will try to have a fun, but deep conversation on how you can, detect and troubleshoot call quality due to network issues. We'll touch on UCCAPI logs, XML, QoE reports, Network Monitor/Wireshark tools. We'll try to have fun with some log based analysis of a call that had or reported issues.
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.