Acceptance Test-Driven Development: Mastering Agile Testing

MF
AM Half day Tutorial
11/11/2013 8:30 AM

"Acceptance Test-Driven
Development:
Mastering Agile Testing"
Presented by:
Nate Oster
CodeSquads, LLC

Brought to you by:

340 Corporate Way, Suite 300, Orange Park, FL 32073
888 268 8770 904 278 0524 sqeinfo@sqe.com www.sqe.com

Nate Oster
CodeSquads, LLC

An agile player-coach and founder of CodeSquads, Nate Oster helps
clients adopt lean and agile methods. Nate builds high-performance teams
that adapt to change, embrace a pragmatic philosophy of continuous
improvement, measure progress with new features, and deliver high-quality
software that delights customers. As a coach, he inspires adopters with
hands-on mentoring and simulations that provide a safe learning
environment for new ideas. Nate promotes testing as a serious technical
discipline. While Nate maintains a speaking schedule at software
development conferences, he spends most of his time as a hands-on
advisor to software product teams from startups to multinationals. Nate is
easily defeated at all card games. Contact him
at NateOster@CodeSquads.com.

MASTERING AGILE TESTING
Nate Oster
CodeSquads LLC

NATE OSTER
Agile Player-Coach &
Founder, CodeSquads
Focused on adopting
Lean & Agile methods
Mail: Nate.Oster@codesquads.com
Twitter: nateoster
Voice: 703.930.4100

LEARNING OBJECTIVES
Stop finding bugs after development!
Shift from tests as verification to
tests as specification by learning to test first.
Simulate the feel of ATDD in a non-threatening way
Gain meaningful practice with table-based and
plain-language formats for specifying intent.
Leave empowered to advocate ATDD
with your own teams and managers!
©CodeSquads LLC “Mastering Agile Testing”

AGENDA

Agile Testing has limits
Simulation: Tests as Veriﬁcation
ATDD Intro or How I Was Dragged Into Testing First
Simulation: Tests as Speciﬁcation


AGENDA

Speciﬁcation by Example
Simulation: Examples using Tables
Simulation: Examples using Given-When-Then
Wrap-up: Action Planning


SIMULATION:
TESTS AS VERIFICATION

SIMULATION:
TESTS AS VERIFICATION
Teams of 3 or 4
“Develop” an image by
punching graph paper
“Test” your solution
by ﬁtting it over pegs
Satisfy your Customer!

ACCEPTANCE TESTDRIVEN DEVELOPMENT
Stop testing bugs out.
Start building quality in.

Anatomy(of(an(Itera-on(
2(–(4(week(-mebox(
Define(

Define(
Build(

Define(
Build(

Build(

Test(

Define(

Test(

Build(

Test(

Define(

Define(
Build(

Test(

Build(

Test(

Define(

Test(

Build(

Test(

Itera-on(Planning…(
Retrospec-ve(
Itera-on(Demo(

Itera-on(Planning(

Feature(
Team(

Build(

Test(

Define(

a(f
(

y…
da
xt(
ne rs(
ou (
2(h ours
(h
2@4

urs

(
urs

ys(
(d a
ew

(h o
ew

a(f

(ho
2@4

(

Nate%Oster,%“The%Agile%Challenge”%Workshop,%CodeSquads%LLC.%


SIMULATION:
TESTS AS SPECIFICATION

SIMULATION:
Start each story by outlining the acceptance criteria
Specify acceptance tests as concrete examples
If we don’t know when we’re done,
then why are we starting?

Hypothesize the top 3 effects of this change

RETROSPECTIVE:
Prepare to Share:

Reﬂect:
Where your
hypotheses correct?
Why or why not?

Appoint a scribe
Share your results
at your tables
List the top
improvements


SPECIFICATION BY EXAMPLE
“An example would be helpful right about now.”
- Brian Marick

Essential

Incidental

Hat tip: Dale Emery


Agile&Tes)ng&Quadrants&
Business-facing Tests

Acceptance Tests

Unit & Component Tests

Automated
Frameworks

Exploratory Tests
Usability Testing
UAT

Performance Testing
Security analysis
“-ility” tests

Technology-facing Tests

Mostly
Manual

Tests that critique the product

Tests that support the Team

Mostly
Automated

Specialized
Tools

“Agile Testing,” Lisa Crispin & Janet Gregory, used with permission (originally Brian Marick, 2006)

The$Test$Automa,on$Pyramid$
Exploratory
/Manual

GUI
More business
facing, realistic

Sn

Acceptance Tests
(API Layer)

FitNesse/
Cuke

Lower-cost
Easier maintenance
Faster feedback

xUnit
Unit & Component Tests

Adapted from Mike Cohn (Automated Test Pyramid) & “Agile Testing”, Lisa Crispin & Janet Gregory..


THE TEST AUTOMATION PYRAMID

Push tests as low as
possible in the pyramid
Have tests focus on
intent, not implementation
Team decides appropriate
level for each test


SOME TOOLS FOR
EXECUTABLE SPECIFICATIONS
TOOL

TECHNOLOGY
SWEET SPOT

FitNesse

Java (native)
.NET (plugin)

Cucumber

Ruby (native)
Java (CucumberJVM)
.NET (plugin)

SpecFlow

.NET (native)

SIMULATION:
USING TABLES

TABLE-BASED
SPECIFICATIONS
(Re)-build a brokerage
pricing engine
Start with the simplest
scenarios using
realistic examples
Be customer-focused!


Pricing.Stocks
Trade Source Ticker Buy/Sell
Internet
GOOG
Buy
Internet
GOOG
Sell
IVR
GOOG
Buy

Order Type
Limit
Limit
Market

Commission?
$9.99
$9.99
$34.99

[expected “$34.99”, actual “$9.99”]


USE REASONABLE DEFAULTS
Eliminate duplication with conventions
Document the conventions with examples!
Trade Source
Internet
Internet
IVR
IVR
Broker
Broker

Ticker Buy/Sell
GOOG
Buy
GOOG
Sell
GOOG
Buy
GOOG
Sell
GOOG
Buy
GOOG
Sell

Order Type
Limit
Limit
Limit
Limit
Limit
Limit


Commission?
$9.99
$9.99
$34.99
$34.99
$44.99
$44.99

PREFER CONCRETE EXAMPLES
OVER ABSTRACTIONS
It’s tempting to save time with abstract examples
We lose time maintaining “smart tests” that must
complete the same calculations as the system.
Abstract
Example

Concrete
Examples

4%

$40, $4000

Y, N

$49.99, $0.00

‘Correct contents’

3 spanish onions’


OPERANDS != CLARITY
Operands and inequalities can actually obscure intent
Each operand conceals at least two test cases
Operand

Concrete
Examples

>180

179,180, 181

<= 180

179, 180

> $1,000

$1,001


Pricing. MutualFunds. NTF. ShortTermRedemption

No Transaction Fee
Mutual Funds
180 days or less
No commission

Ticker
MNTF
MNLD
MFEE

Fund Type
NTF
No-Load
Load

$49.99 fee


Load %
N/A
N/A
4% on Buy

WHAT IF I BUY TWICE
IN 180 DAYS?

TABLES MAY NOT BE EXPRESSIVE
ENOUGH FOR SOME SCENARIOS
What if I buy the same fund
more than once in 180 days?
What if I sell when only part
of the balance is 180 days old?
- Brian Marick

SIMULATION:
USING TEST LINGOS*
*Credit to Patrick Wilson-Welsh and Dawn Cannon
for coining the term!

LINGO-BASED
SPECIFICATIONS

GIVEN - Context
WHEN - Event
THEN - Outcome

THINKING WITH
GIVEN-WHEN-THEN
Scenario: Buying a no-load mutual fund
charges a commission.
Given I do not own fund MNLD.
When I buy $10,000 in fund MNLD,
then the commission is $49.99
and the fee is $0.00.
When I buy fund MNLD,
then the commission is $49.99.

Pricing. MutualFunds.Buy
Scenario: Buy a mutual fund.

Test Funds
Ticker
MNTF
MNLD
MFEE

Fund Type
NTF
No-Load
Load

Load %
N/A
N/A
4% on Buy


GIVEN-WHEN-THEN CAN BE MORE
EXPRESSIVE THAN TABLES
What if I buy the same fund
more than once in 180 days?
What if I sell when only part
of the balance is 180 days old?

- Brian Marick

Mutual Fund Short Term Redemptions
No transaction fee (NTF) funds held 180 days or less are
subject to a Short Term Redemption Fee of $49.99.
Scenario: Part of sale held less than 180 days charges
short term redemption fee.
Given I own 100 shares of MNTF for 181 days
and I own 100 shares of MNTF for 179 days
When I sell 101 shares of MNTF
Then I am charged a short term redemption fee of $49.99.
Scenario: ...

Scenario: Part of sale held less than 180 days charges
short term redemption fee.
Given I own MNTF
|shares| days held |
| 100 | 181 |
| 100 | 179 |
When I sell 101 shares
Then I am charged a short term redemption fee.


NEW FEATURE:
CONCIERGE LEVEL PRICING
Concierge Level pricing is a trial promotion.
It offers selected customers free internet trades if their
total assets exceed $250,000 or if a trade is for more
than $10,000.
Brainstorm acceptance tests for this feature using
tables, given-when-then, or both. Your choice!


Feature: Concierge pricing promotion.
Background:
Given the concierge pricing promotion is active.
Scenario Outline: Buying in a selected account.
Given a selected account with a balance of <total assets>,
when I buy <trade amount> of <ticker>
using source <trade source>,
then the commission is <fee>.
Examples:
| total assets | trade amount | ticker | trade source | fee |
| $499,999 | $10,001
| GOOG | internet
| 0 |
| $500,001 | $1,000
| GOOG | internet
| 0 |
|
|
|
|
|
|

WRAP-UP: CREATE AN
ACTION PLAN

THE PROBLEM

Finding defects is expensive
Rework, Scrap, Delays
Feedback speed is limited


GRASSROOTS FIRST STEPS

The Triad: Use speciﬁcation by example at a
whiteboard with a dev, analyst, and tester
Steel Thread: Try executable speciﬁcations for a
few small bugs or stories
Plant Seeds: Host a brownbag and ask for support


WRAP-UP: CREATE AN
ACTION PLAN
What outcomes could speciﬁcation by example
improve on your teams?
What impediments to adopting spec by example do
you anticipate?
How could you overcome these impediments?
What small experiments will quickly check your thinking
about ATDD on your own teams?

RESOURCES
Learn More:

Experiment:

Speciﬁcation by Example
(Gojko Adzic)
nate.oster@codesquads.com
The Cucumber Book
Twitter:Hellesoy)
(Aslak nateoster
Voice: 703.930.4100
Agile Testing
(Lisa Crispin & Janet Gregory)

“Pull” in support through your
Team’s retrospectives
People & Interactions
over Processes & Tools!

Reach Out:
Nate Oster
noster@keyholesoftware.com
703-930-4100 (m)


MASTERING AGILE TESTING

“Mastering+Agile+Tes/ng+Workshop”+copyright+©CodeSquads+LLC.++All#rights#reserved.
These+materials+are+provided+under+license+to+individual+par/cipants.++Par/cipants+may+
not+reproduce,+alter,+or+build+upon+these+materials.++Par/cipants+may+not+reuse+these+
materials+for+training+purposes.++Slides+and+diagrams+that+are+specifically+iden/fied+as++
licensed+under+a+Crea/ve+Commons+(CCHBY+2.0+unported+license)+may+be+reproduced+
(without+modifica/on)+if+they+retain+the+aOribu/on+provided.+


Acceptance Test-Driven Development: Mastering Agile Testing

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (8)

Ähnlich wie Acceptance Test-Driven Development: Mastering Agile Testing

Ähnlich wie Acceptance Test-Driven Development: Mastering Agile Testing (20)

Mehr von TechWell

Mehr von TechWell (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Acceptance Test-Driven Development: Mastering Agile Testing