CodedUI tests within Visual Studio makes it easy for developers together with tester to create, fully-automated, functional user interface tests. These tests alert the team in an, easy to execute, automated way about regressions. CodedUI tests are easy to create for different UI technologies. But, all kinds of test automation needs an investment. To get a good return on this test automation investment you need to create CodedUI tests in a robust manner which can sustain changes to your application over time. In this session you will see how maintainable CodedUI tests can be created and how the test infrastructure needs to be configured for efficient execution.

1. test automation practices from the field
CODED UI

2. Clemens Reijnen
www.clemensreijnen.nl
@clemensreijnen
clemens.reijnen@sogeti.nl
www.youtube.com/clemensreijnen
www.slideshare.net/clemensreijnen

3. the field
complex user interfaces
big project structures
multiple environments

4. complex user interface
challenges:
many controls
changing controls
complex flow
multiple screens
changing screens
…

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

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

7. multiple UIMap’s
UIMap page object pattern

8. search filter, search and the tree

9. reuse UIMap Helper Class

10. reuse test all controls

11. shared reuse shared steps in Coded UI

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

13. Object Repository:
Keeps UI Object definitions
cuite
separate from automation
code (no more UIMaps)

14. complex user interface
take 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

15. big project structures
challenges:
multiple teams
chain of distributed projects
big teams
short test timeframe

16. big project structures
practices:
team collaboration
branch strategy code and test
versioning test case
no double tests

17. collaborate
work together
__with work packages
__on alm artifacts

18. branch
test same heartbeat as development

19. branch
tests
tests test tests
tests
tests tests
tests
tests tests tests
build
build
build
build

20. Visual Studio test projects
with Coded UI test case
branch

21. UIMap per branch
UIMap’s don’t merge well
branch

22. specific test
automation branch
branch

23. ! well maintained regression set
branch

24. MTM test plans
with or without
associated automation
branch

25. MTM test plans
with or without
associated automation
branch
test cases
test cases
test cases
test cases test cases

26. projects`
Team
Project
Team Team Team Team Team
Project Project Project Project Project

27. double

28. double

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

30. multiple environments
challenges:
test for different environments
no virtualized environments
short test cycles
less time for execution

31. multiple environments
practices:
execute with out SCVVM
test execution responsibility
execute from build on environments

32. infra

33. infra

34. infra configure for load or environments

35. execute

36. build

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

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

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

40. final notes

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

42. soon available

43. 43