Technical meeting automated testing with vs2010

Technical MeetingAutomated Testing with VS2010

Suite of Application Lifecycle Management toolshttp://msdn.microsoft.com/en-us/library/fda2bad5.aspx

application lifecycle managementhttp://www.clemensreijnen.nl/post/2008/02/18/ALM-Definitions.aspx

work together__with work packages__on alm artifacts

Testing LifecycleSee also on www.tmap.net:- The Test Lifecycle Model- The 4 essentials

http://msdn.microsoft.com/en-us/library/bb385832.aspx

Microsoft Test Manager 2010

Test Case ManagementSee also on www.tmap.net: Control Phase

Test Plans Test Suites Test ConfigurationsOrganize the testing effort in a Test Execution PlanCreate dynamic test suites for changing selection criteriaDefine various test configurations and share automation across those

Test (Execution) Plans

Test Plan OrganizationNaming of test plans for agile environments:Iteration number and name and one extra test plan for endto end tests.

Test Configurations

Test Suites

Test Suites OrganizationNaming of test suites for agile environments:Suite per user story (requirement based) and one additionaltest suite for regression tests.(query based?)(test cases are copied to the regression test suite)

Proposed organization

TCM.exe

TCM plan /list

TCM suites /lists planid:16

Share MTM Artifactsmtm://clemenes-pc:8080/tfs/defaultcollection/p:MSF/Testing/testplan/connect?id=19

mtm://<server name>:<port>/<tfs vdir>/<Collection name>/p:<project name>/<center group>/<group specific> Open Test results Open Test Cases (or any work item) Open Test Runs Open Test Plans Connect to test plans mtm://server:8080/tfs/ProjectCollection/p:Project/testing/testcase/open?id=67http://blogs.msdn.com/b/vstsqualitytools/archive/2010/02/09/sharing-content-in-microsoft-test-manager.aspx

Test Case SpecificationSee also on www.tmap.net: Specification Phase

Test Case Shared Steps Test Data IterationsLink test cases and requirements to provide requirement traceabilityData drive test cases with different parametersRefactor common shared steps in test cases

Test Case

Test step types

Test steps Make them descriptive Not every step is a validation step Use the step attachment

Test steps copy-past

Test Data IterationsData drive test cases with different parameters

Test Data Iterations

Test data copy-past

Shared StepsRefactor common shared steps in test casesReduce test maintenance by sharing test steps across test cases

Shared Steps Shared Step candidates?• REUSE – Many steps, reused for many test cases . Benefit: time, retyping, boring work.• EXPECTED CHANGES – for example environment variables change [URL]. Benefit: Time, test cases which need this step are updated automatically, also action recording.• PRE- CONDITIONS – bring the system under test to a certain state and execute the different verifications. Benefit: beside time, you are certain the application under test is in the same state for every test case• BACK TO INITIAL STATE - after test execution bring the environment back to the initial state for new test cases. Benefit: beside time, you are certain the application under test is always in a clean state for new test cases.

Test ExecutionTest RunnerA test that you will want to run multiple times.Different manual tests that contain common steps.Verifying a bug is fixed by using a manual test.

Test Case ExecutionSee also on www.tmap.net: Execution Phase

Test Case Execution

Action recording

TCM run/create

From TCMrun /export id:239 /resultsfile:”c:runresult”

Share with mtm:// mtm://clemens-pc:8080/tfs/defaultcollection/p:MSF/Testing/testrun/open?id=292

Controlling the testing effortBUG’s

File a BUG

Diagnostic Data AdaptersFile a BugFile an Exploratory BugVerify a Bug

Diagnostic Data Adapters

File a BugSubmit a Bug using Test Runner

Ways to file a Bug Submit a Bug from the Test Runner Submit a Bug from the Verify Bugs View Submit a Bug from Test Results for a Test

Verify a BugVerify a Bug Fix Using Microsoft Test Manager

The Bug FlowLink build 2 testplan. T Execute File Bug Verify fix Close orConfigure Data E Manual by using reopencollectors. S Tests playback Bug T Build definition is the intergrationSetup build anddeploy D Resolve Checkin E Bug Build V Deploy

Test Impact

Test ImpactAssign build 2test plan. T Execute Assign Evaluated and reset Execute ExecuteConfigure Data E ‘passed’ ‘NEW’ build tests impacted by ‘passed’ ‘passed’collectors. S Tests 2 Test Plan code churn Tests Tests T Build definition is the intergrationSetup build anddeploy D Make Checkin E code Build V changes Deploy

Create test from Bug

File an Exploratory BugSubmit an Exploratory Bug using Test Runner

PRO: - Reuse scenario knowledge business user - No typing detailed test steps - Easy to parameterize1 Record scenario by business user with - Writing standards for test steps MTM on application under test. Action - MTM capabilities in step 3. (bug, codedUI, recommended test etc …) recording is captured. Most benefit during step 2 (test case writing), benefit in step 1: run once in common situation. Benefit in step 3: common MTM benefits (record playback, fast forward, parameters etc) and benefit of well written steps.2 Create test steps (with parameters) in MTM by using the action recording. CON: - Manual actions and tests. - Test steps text are technical names - Action recording (step 1) must be clean. - Unknown what is validated, during step 2, need additional knowledge. - The business user must think of the important scenarios3 Save test case and execute it by a tester The action recording during step 1 can have on application under test, by using MTM. unnecessary steps, these can be removed during the execution (1) or during the specification (2).

RECAPTest Activities Planning…

Test Case Management RECAP

RECAPTest Case Specification

RECAPTest Case Execution

Test Case Management RECAP

Intellitrace

1Open the employee applicationSet the intellitrace optionsSet a breakpoint at …

2When on the breakpoint, save the trace file on your desktop

3Close Visual Studio and double click the intellitrace file

4In the intellitrace summary, open the main threat …

5 … and search for The values that where entered during the previous run.

6And now from Microsoft Test Manager

6Set the diagnostic adapter

7Configure the build… it needs a drop location for the symbols (pdb files)

8Run the test case and see it crash… file a bug.

9See the itrace file in the bug report...

10Close MTM, open VS (with or without the employee application).Got to the bug and click the itrace file…See the exception andstart debugging…

11Go back in time

11Go back in time … and find the entered values

Regression Test CandidatesSee also on www.tmap.net: Completion Phase

Test Automationmet Visual Studio 2010 Test automation Where? When? How? Who? Why? What?

Where? When? How? Who? Why? What?

VS2010 Test ToolsUI Test Automation Capabilities Fast Forward CodedUI Test Infrastructure

Test Automation Investment Levels 0 No investment in any kind of automation. Just click and test. 1 Clean up of the Action log maybe re-execute, for more smooth Fast Forward. 2 Basic CodedUI. Only use the default generation, add your own assertion. 3 Advanced CodedUI. Customize the CodedUI and UIMap for optimization.

1 Clean up of the Action

2 Basic CodedUI VS2010 ALM MTLM usages patterns for Windows Azure hosted application development

3 Advanced CodedUI

Fast Forward

Cleaning the action recordingWhen: executing the same test case onmultiple environments or when using test dataiteration or … and don’t forget the sharedsteps

CodedUI

CodedUIfrom existing action recording from Manual Tester

CodedUIfrom existing action recording from Manual Tester 2 1 4 3

CodedUICreate a new action recording by Developer

Data-DrivenCoded UI Test

Test InfrastructureWhere and how to run the automated test?

Test EnvironmentsSee also on www.TMap.net:- Checklist "Intake Test Environment“- Checklist "Test Environment“- Infrastructure Phase

Test labVisual Studio 2010 Lab Management

Where and how to run the automated test?physical test environmentsvirtualized test environments

physical test virtualized testenvironments environments MTLM Client MTLM Client Physical Test Client TFS 2010 System Center Virtual TFS 2010 Machine Manager (SCVMM) Hyper-V Library Physical Host Shares Test Client VM VM share share

Build application physical test environments versus virtualized test environments ProvisionRun tests ‘clean’ env Deploy application

Lab for PhysicalEnvironments, thedifferent flavors…Visual Studio Team Foundation ServerTest Manager Build Server Test Agent Test Agent Test Agent

Configurations for automated test execution: AFlavor A: Execution from VS2010… Real developer test / test automation dry run (Triggered by: right mouse click – run tests, in test project) http://msdn.microsoft.com/en-us/library/dd286580.aspx No additional configuration needed* * Data Diagnostic Settings in the Local.Testsettings file are configurable. Pro: Con: Easy setup No collection of test results in TFS Debug-able test automation Run on developer environment

Configurations for automated test execution: BFlavor B: Execution during build with Build controller… not recommended, strange to run UI tests on build Part of Build Verification Tests (triggered by: build) Set the Build Service to run in interactive mode http://blogs.msdn.com/b/mathew_aniyan/archive/2009/05/26/coded-ui-test-in-a-team-build.aspx Configure the build to run the tests http://msdn.microsoft.com/en-us/library/ms182465.aspx#CreateBuildType * Data Diagnostic Settings in the *.Testsettings file are configurable. Pro: Con: Easy setup No collection of test results in TFS Test results in build result Build Controller needs to run in interactive mode Tests are executed on build environment Run on build environment

Configurations for automated test execution: CFlavor C: Execution during build with Test controller… B Preferred configuration above flavor Part of Build Verification Tests on multiple test agents (triggered by: build) Configure Test Controller (don’t register it with a project collection ) http://msdn.microsoft.com/en-us/library/dd648127.aspx#TestControllers Configure Test Agents on clients (interactive mode) http://msdn.microsoft.com/en-us/library/dd648127.aspx#TestAgents Configure *.Testsettings file in solution to use Test Controller and Test Agents Configure the build to run the tests (see B) Pro: Con: Test run on test environments No collection of test results in TFS Tests run on multiple environments Harder to configure Test Results in Build result Need for specific test client environments Test Settings from VS

Configurations for automated test execution: DFlavor D: Execution from Microsoft Test Manager…than BVT Other type of test Part of Regression Tests (triggered by: MTM user, right mouse click on test case, run) Configure Test Controller (register it with a project collection ) Configure Test Agents on clients (interactive mode, can be the same as MTM) Configure Lab Center in MTM to use test controller and create test ‘agent’ environment. http://msdn.microsoft.com/en-us/library/ee390842.aspx http://msdn.microsoft.com/en-us/library/dd293551.aspx Associate CodedUI test with WI Test Case from VS. http://www.richard-banks.org/2010/11/how-to-use-codedui-tests-watin-and-mtm.html Pro: Con: Test run on test environments Manually triggered by Tester Tests run on multiple environments Hard to configure Test Result in MTM and TFS Need for specific test client (same as MTM?) Test Settings from MTM

Configurations for automated test execution: EFlavor E: Execution from MTM duringPreferred configuration above flavor C Build… Part of BVT Flavor D and E can be configured together (triggered by: Build) Configure Test Controller (register it with a project collection ) Configure Test Agents on clients (interactive mode, can be the same as MTM) Configure Lab Center in MTM to use test controller and create test ‘agent’ environment. Associate CodedUI test with WI Test Case from VS. Create Build task to run TCM or MSTEST task for Test Plan http://blogs.microsoft.co.il/blogs/shair/archive/2010/10/30/how-to-run-coded-ui-tests-from-command-line.aspx Pro: Con: Test run on test environments Hard to configure Tests run on multiple environments Need for specific test client (same as MTM?) Test Result in MTM and TFS Triggered by build

Test Controller

Test Agent

New physical environment

Execute CodedUIDuring the build with Visual Studio 2010

Configurations for automated test execution: CFlavor C: Execution during build with Test controller… B Preferred configuration above flavor Part of Build Verification Tests on multiple test agents (triggered by: build) Configure Test Controller (don’t register it with a project collection ) http://msdn.microsoft.com/en-us/library/dd648127.aspx#TestControllers Configure Test Agents on clients (interactive mode) http://msdn.microsoft.com/en-us/library/dd648127.aspx#TestAgents Configure *.Testsettings file in solution to use Test Controller and Test Agents Configure the build to run the tests (see B) Pro: Con: Test run on test environments No collection of test results in TFS Tests run on multiple environments Harder to configure Test Results in Build result Need for specific test client environments Test Settings from VS

1Configure Test Controller.

2Add new Test Settings fileSet remote execution andtest controller.

3Create a new build definitionSet the Automated Test Properties

4Queue a new BuildWatch the Test Agent andTest Environment

Execute CodedUIWithin a test case as an associated automation manualy

Configurations for automated test execution: DFlavor D: Execution from Microsoft Test Manager…than BVT Other type of test Part of Regression Tests (triggered by: MTM user, right mouse click on test case, run) Configure Test Controller (register it with a project collection ) Configure Test Agents on clients (interactive mode, can be the same as MTM) Configure Lab Center in MTM to use test controller and create test ‘agent’ environment. http://msdn.microsoft.com/en-us/library/ee390842.aspx http://msdn.microsoft.com/en-us/library/dd293551.aspx Associate CodedUI test with WI Test Case from VS. http://www.richard-banks.org/2010/11/how-to-use-codedui-tests-watin-and-mtm.html Pro: Con: Test run on test environments Manually triggered by Tester Tests run on multiple environments Hard to configure Test Result in MTM and TFS Need for specific test client (same as MTM?) Test Settings from MTM

1Configure Test Controller.

2Associate the CodedUIwith a Test Case.

2Create Test Environment

3Set test Settings

4Associate the CodedUIwith a Test Case.

5Run Automated Tests from Test Manager

Execute CodedUIWithin a test case as an associated automation from the build

Configurations for automated test execution: EFlavor E: Execution from MTM duringPreferred configuration above flavor C Build… Part of BVT Flavor D and E can be configured together (triggered by: Build) Configure Test Controller (register it with a project collection ) Configure Test Agents on clients (interactive mode, can be the same as MTM) Configure Lab Center in MTM to use test controller and create test ‘agent’ environment. Associate CodedUI test with WI Test Case from VS. Create Build task to run MTC or MSTEST task for Test Plan http://blogs.microsoft.co.il/blogs/shair/archive/2010/10/30/how-to-run-coded-ui-tests-from-command-line.aspx Pro: Con: Test run on test environments Hard to configure Tests run on multiple environments Need for specific test client (same as MTM?) Test Result in MTM and TFS Triggered by build Test Settings from MTM

Execute automated test cases ondifferent environments

0Same steps as previous.

1Configure additional environments in Test Plan properties. Win 7 IE9 configuration Win 7 IE8 configuration TC MTLM Client Win 7 IE8 configuration Physical Test Client TFS 2010 Win 7 IE9 configuration Physical Test Client

1Get Test Plan IDGet Test SuiteGet Test Configurations with TCM.exe

2Create command line for Test Run for the different Test Configurations "run /create /title:""Run on Host for specific Test Point"" /planid:16 /querytext:""SELECT * FROM TestPoint WHERE ConfigurationId=13"" /settingsname:""Automated Test on Windows 7 Environment IE9"" /testenvironment:""Win 7 IE9"" /collection:http://clemenes- pc:8080/tfs/defaultcollection /teamproject:EmployeeApplication" "run /create /title:""Run on test env for specific Test Point"" /planid:16 /querytext:""SELECT * FROM TestPoint WHERE ConfigurationId=12"" /settingsname:""Automated Test on Windows 7 Environment IE8"" /testenvironment:""Win 7 IE8"" /collection:http://clemenes- pc:8080/tfs/defaultcollection /teamproject:EmployeeApplication"

3Add build commands

6Queue a new BuildWatch the Test Agent andTest Environment

Build application ProvisionRun tests ‘clean’ env Deploy application

VS2010 Lab Management• Reproduce the exact conditions of a bug or other development issue.• Build, deploy, and test applications automatically in a clean environment.• Reduce the time required to create and configure machines for testing an application.• Run multiple copies of a test or development at the same time.• Enable members of a team to create and manage virtual environments without requiring system administrator privileges.

MTLM ClientTFS 2010 System Center Virtual Machine Manager (SCVMM) Hyper-V Library Host Shares VM share VM share

VMLab Agent

TFS 2010

staat voor resultaat

http://www.clemensreijnen.nl	2737
http://clemensreijnen.nl	308
http://feeds.feedburner.com	82
http://www.techgig.com	50
url_unknown	4
https://twitter.com	1
http://paper.li	1
http://twitter.com	1
http://webcache.googleusercontent.com	1
http://cache.baidu.com	1

Technical meeting automated testing with vs2010

by Clemens Reijnen on Jul 10, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

10 Embeds 3,186

Statistics

Technical meeting automated testing with vs2010 — Presentation Transcript