Agile Test Automation

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Session 902Agile Test Automation

Werner Keil, Director, Creative Arts & Technologies

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Agenda

25 minutes• Intro• Process• Tools• Framework

30 minutes• Demo• Q&A

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Intro

Main Trend:

Move away from Waterfall to Lean and Agile

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Intro

How does Agile affect

Software Testing?

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Agile Values and Principles

Values• Communication• Simplicity• Feedback• Courage• Respect• Transparency• Trust

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Agile Values and Principles

Principles• Eliminate Waste• Build Quality In• Create Knowledge• Deliver Fast• Respect People• Optimize the Whole

Agile Manifesto

In February 2001, 17 software developers met at a ski resort in Snowbird, Utah, to discuss lightweight development methods. They published the "Manifesto for Agile Software Development" © agilemanifesto.org

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

© solarnavigator.net

ASalt Lake

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

© Gujarat Tourism Bureau

AnotherSalt Lake

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Roles

Roles in an Agile team• Product Owner• Domain Expert• Developer• Tester

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Roles

Tester’s role in a new Agile world

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Responsibilities

• Requirements Management and Analysis• Helping Business with Requirements• Helping Developers with Test Data

preparation and Unit Testing

• Test Execution• Test Automation• Exploratory Testing

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Responsibilities

No more QualityPolice!

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Responsibilities

Build Quality in• Whole team responsible for quality

• Not just Test Engineers• TDD

• Tester as Helper• Aim for zero defect rate

• Though some may call that insane ;-)

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Technical Practices

• Iterative process• Continuous integration• Refactoring

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Process

The Four D’s of Agile Development• Discuss• Decide• Develop• Demonstrate

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Process

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Tools

Test Harness• JUnit• TestNG• etc.

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Tools

Driver• Selenium | WebDriver• SoapUI• Arquillian• etc.

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Tools

Functional• Concordion• FitNesse• Cucumber• easyB• Eclipse Jubula• etc.

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Selenium 2

Selection Criteria• Self Contained• Browser Support• Scripting in Java

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Selenium 2

This won‘t work

at least

under

Windows

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Concordion

No acceptance tests written like this...

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Concordion

Write them like this instead...

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Concordion

Clear tests lead to clear fixture code

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Concordion

Active Specification• Plain English requirements• Acceptance tests in form of real life

examples• Can be executed against SUT

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Framework

Pages

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Framework

Personas?

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Framework

PersonasFictional – but realistic – character sketches

based on a break-down of the target audience into groups of users that exhibit common characteristics. They are created using knowledge drawn from previous research, for example user groups and surveys that have been carried out with actual users.

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Framework

Testing

Cloud

DEMOTime for a

© 2010-2011 Creative Arts & Technologies | Portions © 2010 Kostya Marchenko, David Peterson | All Rights reserved.

Thank you for attending this session.

Please fill out an evaluation form and place it in the box located at the

back of the room.