Acceptance Test Driven Development for .Net

me => (Ryan Cromwell)

Coder Agile Coach ALM MVP

Acceptance Test Driven Development (ATDD) is a practice in which the whole team collaboratively discusses acceptance criteria, with examples, and then distills them into a set of concrete acceptance tests before development begins. - Elisabeth Hendrickson

• TDD + 1! • Confidence • Collaboration Requirements Design Code Test

No content

“Selenium automates browsers.” http://seleniumhq.org/

IDE • Record and Playback • Create quick bug reproduction scripts • Create scripts to aid later automation • Not scalable WebDriver • Create robust regression scripts • Scale and distribute scripts across many environments • API (Java, .Net, Ruby, Javascript, Python, others)

http://bit.ly/selenese

No content

BDD – Behavior Driven Development Gherkin – Given, When, Then… plus others Top of the testing pyramid http://specflow.org/

No content

No content

No content

Code Or It Didn’t Happen

No content

Good • Given I go to Address Book • When I Quick Add John Doe • And I Quick Add John Doe • Then I’m told of the duplicate Bad • Given I Go To • When I Type John Doe • And hit Save • And I type John Doe • And hit Save • Then I see “Sorry, duplicate”

• Refactor • Consolidate Url Knowledge • SOLID+

• Will Feel Silly • Methods = Features/Behaviors • Single Dom throws a

• TFS Test Controllers & Agents • Selenium Grid • SauceLabs

• VMM Templates • PowerShell • Script Seed Data

Selenium (install-package Selenium.WebDriver) Selenium Helpers (install-package Selenium.Support) SpecFlow (install-package specflow, specflow.org) NUnit (install-package nunit)* ShouldFluent (install-package)*

Test Code is Production Code Discipline Confidence

No content

github.com/cromwellryan

@cromwellryan blog.cromwellhaus.com