Your SlideShare is downloading. ×
Using Models To Ease The Start Up Of Automated
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Using Models To Ease The Start Up Of Automated


Published on

EclipseCon presentation on models in testing

EclipseCon presentation on models in testing

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Using models to ease the start up of automated GUI testing Achim Lörke, Bredex GmbH © 2008 Bredex GmbH Version 2.3
  • 2. Agenda The importance and difficulty of testing early Using models Why models are useful for GUI testing  Aims when using models  Generating structures and sequences  How the test process benefits from using models 03.03.2009 2 MBT
  • 3. Testing early Finding errors early reduces costs Problems with testing early Lack of information on implementation  Workflows unknown  Where to start  How abstract/specific should tests be?  Don‘t start without a plan Redundancy  Maintenance problems  03.03.2009 3 MBT
  • 4. Models can help Design phase involves models Use case diagrams, activity diagrams  UML  Use as foothold for test design Test and development team work from same source  Models have right level of specificity Independent of implementation  Fundamental details about application  Workflows depicted in activity diagrams   models don‘t have to be too formal  03.03.2009 4 MBT
  • 5. What are we aiming for? Complete, functional tests? No!  Identify structures and sequences Basis for automated test  03.03.2009 5 MBT
  • 6. Structure and sequence Use cases provide structure What needs to be tested  Functions and behavior of software  Pre and post conditions of user actions   Tests planned to cover these functions  Activity diagrams show sequences Alternative workflows through application  Show which structures will be reused in application   Tests designed to capture reusability at test case level  03.03.2009 6 MBT
  • 7. Example 03.03.2009 7 MBT
  • 8. Example (cont.) 03.03.2009 8 MBT
  • 9. Example (cont.) 03.03.2009 9 MBT
  • 10. Example (cont.) 03.03.2009 10 MBT
  • 11. Generating test design from models Eclipse Modeling Framework Unified way to share models  Across platforms, tools and model types  Use case diagrams from Eclipse Modeling Tools  domain specific models (e.g. test specifications) 03.03.2009 11 MBT
  • 12. Benefits Same source for test and development Nothing forgotten  Clues about how to modularize tests in model   well thought out test design, easier maintenance  Test team has access to models Errors found and fixed in design phase  03.03.2009 12 MBT
  • 13. Benefits Information on critical areas The more a structure is reused, the more critical it is  Maximum benefit with minimum effort Write tests once and reuse for recurring structures  Earliest possible start with testing Test design created early  Automation begins as soon as tools/process allow  03.03.2009 13 MBT
  • 14. Questions? … More information Booth 204 in the exhibition hall 03.03.2009 14 MBT