Visual Studio 2010 Test Edition

Visual Studio 2010 Test Edition : 

Visual Studio 2010 Test Edition Ravi Kumar . K Test Engineer ZenQA

Agenda : 

Agenda Introduction Cooperation between Roles Cooperation in Application LifeCycle Test Goals Test Roles Democratizing ALM Test Impact View Camano Test Runner CodedUI Conclusion

Introduction : 

Introduction Testing is an important role Seperation in the area of tooling Cooperation is hard to find even though it offers many advantages Cooperation increases the efficiency of the entire application life cycle Visual studio 2010 Improves upon the cooperation between software development and testers

Cooperation between Roles : 

Cooperation between Roles Cooperation does not happen automatically Consequence of this virtual wall is disastrous for quality Many bugs are caused especially by unclear specifications

Contd.. : 

Contd..

Cooperation in Application Lifecyle : 

Cooperation in Application Lifecyle The Virtual wall causes confusion, irritation and loss of quality Software Development and all roles involved are supposed to strive for one common goal

Contd.. : 

Contd.. Synergy between roles, processes and tools is also commonly known as Application Lifecycle Developers and testers would have more insight in each other’s work and challenges VS Team System 2010 will better this cooperation Cooperation not only occurs by giving insight in work activities, but also by working on common products

Test Goals : 

Test Goals Monolith had all of its functionality in a compact manner in one big component Each phase of the development process has its own test goals and depth of test coverage Unit testing Integration testing System testing Acceptance testing

Test Roles : 

Test Roles Development Tester System Tester Acceptance Tester

Democratizing ALM - Vision : 

Democratizing ALM - Vision Extended the support of VS2010 for ALM Most remarkable added feature – CAMANO Ability to record the actions done by tester – Test Runner Gathers infomation about the system that is tested on VSTE has the option to automate the execution of acceptance tests Introduced CodeUI technology UI tests can be included in daily or continous build process

Test Impact View - development tester. : 

Test Impact View - development tester. Provided with ample tools in current and previous versions Microsoft found new ways to support the work of development testers Test Impact analysis is the most eye-catching Provides an overview of all unit tests that have been affected after a code change Provides an overview of code that has been modified

Camano : 

Camano Problem: Test cases are based upon Business Req.. Change in Business requirements causes a problem to tester Solution: In VS2010, Linking test cases to requirements Camano is a new tool that allows a tester to create and organize the test cases for a given project Camano tell if requirement do not have a test case yet and vice versa

Contd.. : 

Contd.. Above is a screen snapshot of creating a test case in Camano

Contd.. : 

Contd.. Camano has an impact view that shows which tests need to be rerun

TEST RUNNER : 

TEST RUNNER We’ve talked about the new tool "Camano" to define your test cases and create test suites Load the tests into team team system Now execute the test cases with the test runner

Contd.. : 

Contd.. Three record settings

Contd.. : 

Contd.. Run the test – Last step failed Capture the screen to show exactly what we see

Contd.. : 

Contd.. Create a new bug Data collected already being pre populated and placed the bug report

Contd.. : 

Contd.. Replay the recording to re-test the application after the bug is fixed Steps that we used to test the webpage are now reexecuted automatically

CodedUI : 

CodedUI Introduced a new tool for creating scripts to automate User Interface Able to generate the code automatically Able to automate load tests, regression tests, and user test

Create CodedUI Test : 

Create CodedUI Test

Contd.. : 

Contd..

Contd.. : 

Contd..

Contd.. : 

Contd..

Contd.. : 

Contd..

Contd.. : 

Contd..

Contd.. : 

Contd..

Contd.. : 

Contd..

Contd.. : 

Contd..

Conclusion : 

Conclusion All test roles are provided with clear and better support Use integrated tools that are used by architects and developers A clear speration of roles, tasks and authorizations are necessary Structured approach determines how successful you are with your test strategy

Questions : 

Questions