atdd mit concordion und webdriver€¦ · atdd mit concordion und webdriver © opitz consulting...

© OPITZ CONSULTING GmbH 2011 Seite 1ATDD mit Concordion und WebDriver

ATDD mit Concordion und WebDriver


Müller, Torsten

OPITZ CONSULTING Berlin GmbH

Berlin, 07 April 2011

ATDD mit Concordion und WebDriver


Einleitung

“ATDD is hard work”

“The complexity and effort

of automating acceptance tests

easily matches – and often outweighs –

that of implementing the story itself.”

JASON GORMAN: ANTWORT AUF BRIAN MARICK: BARRIERS TO ACCEPTANCE-TEST DRIVEN DESIGN

http://www.exampler.com/blog/2008/08/19/barriers-to-acceptance-test-driven-design













Agenda

1. Akzeptanztest-getriebene Entwicklung (ATDD)

2. Tools

Concordion

WebDriver

3. (Best?) Practices

WebDriver

Concordion

Test Automation


1 Akzeptanztest-getriebene Entwicklung (ATDD)


Begriffsdefinition

Entwicklungspraxis, in der

die funktionalen Anforderungen (Akzeptanzkriterien)

einer User Story

als konkrete und automatisierbare

(praxisrelevante) Beispiele

vor der eigentlichen Entwicklung der Story

selber geschrieben werden.

WIECHMANN ET AL.: ATDD KURZ ERKLÄRT – DIE RICHTIGEN DINGE ENTWICKELN

http://www.projekt-log.de/agile_softwareentwicklung/atdd-in-a-nutshell/











Gegenstand

„Specification by Example“

„Example Driven Development“

GOJKO ADZIC: SPECIFYING WITH EXAMPLES

http://gojko.net/2008/11/04/specifying-with-examples/







Prozess

DAVID PETERSON: STORY DELIVERY LIFECYCLE

http://www.concordion.org/memo/StoryDeliveryLifecycle.pdf



Abgrenzung: ATDD und Abnahmetests

Abnahmetest oder auch User Akzeptanztest (UAT)

Fokus: Test der gelieferten Software durch den Kunden bzw. Auftraggeber

Ziel: Abnahme der Software

Akzeptanztest-getriebene Entwicklung

Fokus: Kommunikation zwischen Product Owner und Entwicklungsteam

Ziel: Entwicklung der „richtigen“ Software


Abgrenzung: ATDD und TDD

LASSE KOSKELA: ACCEPTANCE TDD EXPLAINED

http://www.methodsandtools.com/archive/archive.php?id=72



Anwendungsbereiche

NIGEL CHARMAN: WHAT TYPES OF APPLICATION CAN I TEST WITH CONCORDION?

http://tutansblog.blogspot.com/2009/06/what-types-of-application-can-i-test.html















Automatisierung

“Acceptance tests should run

in an environment

as close to the

production environment

as possible.”


Tool-Einsatz

WebDriver

Concordion


2Tools


2.1Concordion


Concordion

“Lets you write business tests that don't assume

a particular implementation.”

PROJECT WEBSITE

http://www.concordion.org/



Funktionsweise

PROJECT WEBSITE




Beispiel – Spezifikation


Beispiel – Instrumentierung


Beispiel – Fixture


Beispiel – JUnit-Integration

ConcordionRunner

ConcordionBuilder


Screenshot Extension

attach screenshots to help

diagnose test failures

add screenshots to the output

for documentation purposes

Erweiterungen: Screenshot Extension


Logging Tooltip Extension

provide more insight into what

the tests are actually doing

Erweiterungen: Logging Tooltip Extension


2.2WebDriver


WebDriver

“WebDriver is a tool

for automating testing web applications,

and in particular

to verify that they work as expected.”

“It aims to provide a friendly API that’s

easy to explore and understand,

which will help make your tests

easier to read and maintain.”

PROJECT WEBSITE

http://seleniumhq.org/docs/03_webdriver.html


Beispiel


3(Best?) Practices


3.1WebDriver


WebDriver Practices

Name Everything

Waiting, Waiting, Waiting…

Turn UI Testing into API Testing

Always Have A Plan B. And A Plan C. (And D…)

Take Screenshots If Something Goes Wrong

Use Diagnostic Logging

THOMAS SCHRANTZ: UI AUTOMATION: TRICKS AND TRAPS

http://www.mathpirate.net/log/2009/12/23/ui-automation-tricks-and-traps/











„Name Everything”


„Waiting, Waiting, Waiting…”



Window Licker (http://code.google.com/p/windowlicker/)

http://code.google.com/p/windowlicker/


„Turn UI Testing into API Testing”

Introduce Page and (optional) Site Objects


„Turn UI Testing into API Testing”: Page Objects

SIMON STEWARD: PAGE OBJECTS

http://code.google.com/p/selenium/wiki/PageObjects



„Turn UI Testing into API Testing”: Page Objects

Hide low level implementation details

Methods represent the services that the page offers

loginPage.loginAs(String user, String credentials);

searchPage.searchFor(String query);

Methods return other page objects

SearchResultsPage resultsPage =

searchPage.searchFor(String query);

Different results for the same action are modeled

as different methods

RefineSearchPage refineSearchPage =

searchPage.searchForButExpectNoMatches(String query);


Page Objects: WebDriver Support

PageFactory(Package org.openqa.selenium.support)

LoadableComponent & SlowLoadableComponent(Package org.openqa.selenium.support.ui)


„Always Have A Plan B. And A Plan C.”

JavascriptExecutor(Package org.openqa.selenium)


„Take Screenshots”

TakesScreenshot(Package org.openqa.selenium)


„Diagnostic Logging”

EventFiringWebDriver & WebDriverEventListener(Package org.openqa.selenium.support.events)


3.2Concordion


Concordion Practices

“The closer your acceptance tests

are to the business rules,

the more stable they are.”

GOJKO ADZIC: HOW TO IMPLEMENT UI TESTING WITHOUT SHOOTING YOURSELF IN THE FOOT

http://gojko.net/2010/04/13/how-to-implement-ui-testing-without-shooting-yourself-in-the-foot-2/

DAVID PETERSON: CONCORDION – HINTS AND TIPS

http://www.concordion.org/Technique.html


























Concordion Practices

Think Given-When-Then

Write Specifications, not Scripts

Use S.M.A.R.T. Examples

Think in Goals, Tasks and Actions

Evolve a Scripting DSL

DAVID PETERSON: CONCORDION – HINTS AND TIPS




„Think Given-When-Then“

Scenario: <A scenario specific goal>

GIVEN <something that needs to have happened or be true>

WHEN <some task I must do>

THEN <some way I know I've achieved my goal>


„Write Specifications, not Scripts“

Scenario: Search for the Concordion homepage

Given I am at http://google.com

When I enter "concordion" into the search field and click "Search"

Then the top result should say "Concordion”

Better Scenario: Search for the Concordion homepage

When I search for "concordion"

Then the top result should say "Concordion"


„Use S.M.A.R.T. Examples“

SPECIFIC

Examples are explicitly defined and definite.

MEASURABLE

The result is observable and quantifiable.

ACHIEVABLE

Examples describe a realistic scenario.

RELEVANT

Examples are related to the particular story.

TIME-BOUND

The result can be observed in a defined Time.

NARESH JAIN: ACCEPTANCE TEST DRIVEN DEVELOPMENT

http://www.slideshare.net/nashjain/acceptance-test-driven-development-350264











„Think in Goals, Tasks and Actions“

GOAL: What we’re trying to achieve which has one or more…

TASKS: The high-level work-item that we complete to fulfill the

goal, each having one or more…

ACTIONS: The specific steps or interactions we execute to complete

the task.

GOALS, TASKS Spezifikation

ACTIONS Fixture

MARCANO, ANTONY: A BIT OF UCD FOR BDD & ATDD: GOALS -> TASKS -> ACTIONS

http://antonymarcano.com/blog/2011/03/goals-tasks-action/







„Evolve a Scripting DSL“

DAVID PETERSON: WHAT DO I MEAN BY A „SCRIPTING DSL“?

http://blog.davidpeterson.co.uk/2008/02/what-do-i-mean-by-scripting-dsl.html















„Evolve a Scripting DSL“

GIVEN

Encapsulate test data creation

Object Mother, Test Data Builder

Make It Easy (http://code.google.com/p/make-it-easy/)

WHEN

Turn UI Testing into API Testing

Page Objects (http://code.google.com/p/selenium/wiki/PageObjects)

THEN

Encapsulate Assertions

Hamcrest (http://www.code.google.com/p/hamcrest/)

http://code.google.com/p/make-it-easy/






http://www.code.google.com/p/hamcrest/



3.3Test Automation


Test Automation

VEGARD HARTMANN: SUCCEEDING WITH WEBTESTING USING WEBDRIVER

http://open.bekk.no/wp-content/uploads/2010/03/succeeding-with-webtesting-using-webdriver.pdf













Test Automation Practices

Use Independent Tests

Cleanup, Setup, Test, Teardown

Use Non-Production code for Setup/Teardown

Don't rely on external systems that you don't control

Provide Feedback If Something Goes Wrong

NARESH JAIN: PATTERNS AND ANTI-PATTERNS: ACCEPTANCE TESTING WITH FITNESSE

http://blogs.agilefaqs.com/2007/08/25/patterns-and-anti-patterns-acceptance-testing-with-fitnesse/

















Fragen und Antworten


Referenzen


Referenzen

Adzic, Gojko:

Bridging the Communication Gap: Specification by Example and

Agile Acceptance Testing

London : Neuri Limited; 2009. ISBN 978-0955683619

Freeman, Steve; Pryce Nat:

Growing Object-Oriented Software, Guided by Tests

Amsterdam : Addison-Wesley Longman; 2009.

ISBN 978-0321503626


Referenzen

Adzic, Gojko: How to implement UI testing without shooting

yourself in the foot

http://gojko.net/2010/04/13/how-to-implement-ui-testing-without-

shooting-yourself-in-the-foot-2/

Adzic, Gojko: Specifying With Examples


Charman, Nigel:

What types of application can I test with Concordion?

http://tutansblog.blogspot.com/2009/06/what-types-of-application-

can-i-test.html

Gorman, Jason: Antwort auf

Marick, Brian: Barriers to acceptance-test driven design

http://www.exampler.com/blog/2008/08/19/barriers-to-acceptance-

test-driven-design






















































Referenzen

Hartmann, Vegard:

Succeeding with webtesting – Using WebDriver

http://open.bekk.no/wp-content/uploads/2010/03/succeeding-with-

webtesting-using-webdriver.pdf

Jain, Naresh: Acceptance Test Driven Development

http://www.slideshare.net/nashjain/acceptance-test-driven-

development-350264

Jain, Naresh: Patterns and Anti-Patterns: Acceptance Testing with

FitNesse

http://blogs.agilefaqs.com/2007/08/25/patterns-and-anti-patterns-

acceptance-testing-with-fitnesse

Koskela, Lasse : Acceptance TDD Explained







































Referenzen

Marcano, Antony:

A bit of UCD for BDD & ATDD: Goals -> Tasks -> Actions


Marcano, Antony:

Acceptance tests are more A+S than T+G

http://www.testingreflections.com/node/view/6704

Peterson, David: Concordion – Hints and Tips


Peterson, David: Story Delivery Lifecycle


Peterson, David: What do I mean by a „Scripting DSL“?

http://blog.davidpeterson.co.uk/2008/02/what-do-i-mean-by-

scripting-dsl.html






http://www.testingreflections.com/node/view/6704

















Referenzen

Pryce, Nat:

Test Data Builders: an alternative to the Object Mother pattern

http://nat.truemesh.com/archives/000714.html

Schrantz, Thomas: UI Automation: Tricks and Traps

http://www.mathpirate.net/log/2009/12/23/ui-automation-tricks-and-

traps

Steward, Simon: Page Objects


Wiechmann, Robert et al.:

ATDD kurz erklärt – Die richtigen Dinge entwickeln

http://www.projekt-log.de/agile_softwareentwicklung/atdd-in-a-

nutshell/

http://nat.truemesh.com/archives/000714.html

http://www.mathpirate.net/log/2009/12/23/ui-automation-tricks-and-traps




















Referenzen

Concordion: http://www.concordion.org/ Logging Tooltip Extension

http://www.concordion.org/extensions/LoggingTooltipExtension.html

Screenshot Extension

http://www.concordion.org/extensions/ScreenshotExtension.html

WebDriver: http://seleniumhq.org/docs/03_webdriver.html

Make It Easy: http://code.google.com/p/make-it-easy/

Hamcrest: http://www.code.google.com/p/hamcrest/

Window Licker http://code.google.com/p/windowlicker/


http://www.concordion.org/extensions/LoggingTooltipExtension.html

http://www.concordion.org/extensions/ScreenshotExtension.html

http://seleniumhq.org/docs/03_webdriver.html







http://code.google.com/p/windowlicker/

atdd mit concordion und webdriver€¦ · atdd mit concordion und webdriver © opitz consulting...

Documents