Coded UI - Test automation Practices from the Field

test automation practices from the fieldCODED UI

Clemens Reijnenwww.clemensreijnen.nl@clemensreijnenclemens.reijnen@sogeti.nlwww.youtube.com/clemensreijnenwww.slideshare.net/clemensreijnen

the fieldcomplex user interfaces big project structuresmultiple environments

complex user interfacechallenges: many controls changing controls complex flow multiple screens changing screens …

complex user interfacepractices: edit the UIMap search and filter reusable ’test’methods reusable test assertions shared steps loose coupling low dependencies

UIMap multiple UIMap’s a map per - screen - scenario - part - team - …

multiple UIMap’sUIMap page object pattern

search filter, search and the tree

reuse UIMap Helper Class

reuse test all controls

shared reuse shared steps in Coded UI

UIMap mix different test projects for tune your manual tests for automation or remove them

Object Repository: Keeps UI Object definitionscuite separate from automation code (no more UIMaps)

complex user interfacetake aways:• reuse steps and assertions• create helper classes• well defined uimap structure• use codeui builder• start from scratch or tune your manual tests• make clear test method names• separate the test intent from the test steps• no related tests• all test must leave the application in the same state

big project structureschallenges: multiple teams chain of distributed projects big teams short test timeframe

big project structurespractices: team collaboration branch strategy code and test versioning test case no double tests

collaborate work together __with work packages __on alm artifacts

branch test same heartbeat as development

branch tests tests test tests tests tests tests tests tests tests tests build build build build

Visual Studio test projects with Coded UI test casebranch

UIMap per branch UIMap’s don’t merge wellbranch

specific test automation branchbranch

! well maintained regression setbranch

MTM test plans with or without associated automationbranch

MTM test plans with or without associated automationbranch test cases test cases test cases test cases test cases

projects` Team Project Team Team Team Team Team Project Project Project Project Project

double

big project structurestake a ways: branch structure /multiple team projects use areas well don’t make it too complex, some things can’t be donetest and developers have the same rhythm

multiple environmentschallenges: test for different environments no virtualized environments short test cycles less time for execution

multiple environmentspractices: execute with out SCVVM test execution responsibilityexecute from build on environments

infra configure for load or environments

execute

multiple environmentstake a ways:multiple environments is possible without SCVVM how are the environments used who executes the tests

Test Automation Investment Levels0 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 Coded UI. Only use the default generation, add your own assertion.3 Advanced Coded UI. Customize the Coded UI and UIMap for optimization.

Test Execution Investment Levels4 Execute them on a single environment.5 Execute them on multiple environments.6 Execute them on virtualized environments.7 …

final notes

interesting read / watchhttp://www.ie.sogeti.com/Product-- http://www.thoughtworks.com/evServices/Software-Testing--QA- ents/maintaining-automated-Services/Test-Automation/ acceptance-tests

soon available

http://www.clemensreijnen.nl	2433
http://clemensreijnen.nl	406
http://feeds.feedburner.com	83
http://webcache.googleusercontent.com	1
http://cache.baidu.com	1

Coded UI - Test automation Practices from the Field

by Clemens Reijnen on Nov 25, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

5 Embeds 2,924

Statistics

Coded UI - Test automation Practices from the Field — Presentation Transcript