Hello. I would like to welcome to this webinar onHow to augment your coded UI environment with Test Automation, to greatly improve the quality of your application software.My name is
ABT separates the Test Cases from the Application under test, through an Easy-to-define Interface
ABT separates the Test Cases from the Application under test, through an Easy-to-define Interface
ABT separates the Test Cases from the Application under test, through an Easy-to-define Interface
ABT separates the Test Cases from the Application under test, through an Easy-to-define Interface
Software testing with Visual Studio 2012 is focused on testing all aspects of your application.Test planning and management, manual testing and exploratory testing are handled from Microsoft Test Manager.Automated testing, unit testing, performance and load testing, and code analysis are handled from the Visual Studio IDE.All aspects of the testing lifecycle are monitored and managed with Team Foundation Server, enabling up to date reporting across the entire project.Extensibility points enable 3rd party solutions, customizable build engines and complex lab environments.This module focuses on Build Automation practices to validate quality at a continuous cadence when developing software as a team.
UI Automation test creation is handled from the Visual Studio IDE. There are three methods for creating these tests: manual creation via code, keyword based scripts (using the preferred partner solution LogiGear), recording your actions as you interact with the UI, or importing an existing manual test case that has an action recording. Once the test has been created in the IDE, it can be ran from the IDE itself directly, from Test Manager, or automated as part of an automated build or deploy scenario. Automated UI tests can be associated with test cases in TFS for maximum visibility. Just like all other types of testing in Visual Studio, automated UI tests are backed by Team Foundation Server, enabling up to the minute detailed reporting. Depending on the method of execution, bugs can be created (directly in the case of MTM execution, or part of a failed build in the case of complete automation).
Talk Track:<see slide>
Talk Track:As coded UI tests are code, you can attach them to your continuous integration build verification tests, or other automated builds to ensure that defects in your application’s UI are discovered as soon as possible.
Talk Track:Teams often worry that reducing their deployment cycle time will reduce overall quality. It’s a real risk, but it can be avoided if you modernize your quality management system as well. With MTM and the Visual Studio 2012 ALM solution, your quality management integrates seamlessly into your modern development platform, ensuring that velocity and quality will go hand in hand.