• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Coded UI - Test automation Practices from the Field
 

Coded UI - Test automation Practices from the Field

on

  • 14,104 views

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, ...

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.

Statistics

Views

Total Views
14,104
Views on SlideShare
7,222
Embed Views
6,882

Actions

Likes
3
Downloads
147
Comments
1

14 Embeds 6,882

http://www.clemensreijnen.nl 6135
http://clemensreijnen.nl 599
http://feeds.feedburner.com 99
https://twitter.com 27
http://www.tuicool.com 13
http://www.clemensreijnen.nl&_=1342627223204 HTTP 1
http://ranksit.com 1
http://cache.baidu.com 1
http://www.slashdocs.com 1
http://webcache.googleusercontent.com 1
http://www.docseek.net 1
http://www.365dailyjournal.com 1
http://www.docshut.com 1
https://www.google.co.in 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • I'm building 'hand-coded' CUITs, which I write about on my blog.

    Some posts:

    -- http://burdettelamar.wordpress.com/2014/04/19/clean-and-dry-verifiers/
    -- http://burdettelamar.wordpress.com/2014/03/21/keep-your-page-objects-dry/
    -- http://burdettelamar.wordpress.com/2014/04/18/object-not-found-log-the-context/
    -- http://burdettelamar.wordpress.com/2014/04/01/encapsulate-the-gui-tool/
    -- http://burdettelamar.wordpress.com/2014/03/21/getters-and-setters/
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

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

    • 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
    • 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
    • infra
    • infra configure for load or environments
    • execute
    • build
    • 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
    • 43