Agile testing - Testing From Day 1

AGILE TESTING
Testing From Day One
By Fadi Stephan

While we wait for the
session to start, meet your
neighbors and discuss …
AGILE TESTING @fadistephan | kaizenko.com
• Do you currently work on an Agile team?
• Does your team include testers?
• What testing challenges are you facing?

Technology Consultant and Certified Scrum Trainer
20 Years of Experience in Software Development
Co-organizer of the DC Scrum User Group (DCSUG)
Skier and Diver
www.kaizenko.com @KaizenkoLLC
@FadiStephan
FADI STEPHAN

Requirement Design Code Test
2 Weeks 2 Weeks 2 Weeks 2 Weeks

4 Weeks
Requirement Design Coooooooooooooooooooooooooode
Test

Code 1 Code 2
Test 1 Test 2
2 Weeks 2 Weeks 2 Weeks 2 Weeks
Code 3 Code 4
Test 3

2 Weeks
Designed
Coded
And
Tested Story 1 Story 1
Story 3
Story 4
Story 6
Story 2
Story 1
Story 2
Story 3
Story 5
Story
Story 4
Story 1
Story 2
Story 3
Story 5
Story 4
Story 1
Story 2
Story 3
Story 5
Story 6
Story 7
Day 1 Day 3 Day 6 Day 7 Day 10

Requirements
Design
Development
Test
DeployWATERFALL
APPROACH

Requirements
Design
Development
Test
Deploy
ITERATIVE &
INCREMENTAL
APPROACH TO
WATERFALL

“Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software.”
“Deliver working software frequently,
from a couple of weeks to a couple
of months, with a preference to the
shorter timescale.”
- First and third of the Twelve Principles behind the Agile Manifesto
A LEANER PMO IN THE FEDERAL GOVERNMENTAGILE TESTING @fadistephan | kaizenko.com

REQUIREMENTS
DESIGN
DEVELOPMENTTEST
DEPLOY

Days
Not
Months or
Years
REQUIREMENTS
DESIGN
DEVELOPMENTTEST
DEPLOY

WHAT KIND OF
TESTING?

Brainstorm with your
neighbors …
What are all the types of testing that
you currently do or should be doing?

Functional Tests
Acceptance Tests
Unit Tests
Integration Test
Component Tests
System Tests
Exploratory Tests
Usability Tests
Performance Tests
Load Tests
Stress Tests
Security Tests
Types of Testing

Functional Tests
Acceptance Tests
Unit Tests
Integration Tests
Component Tests
System Tests
Exploratory Tests
Usability Tests
Performance Tests
Load Tests
Stress Tests
Security Tests
SupportProgramming
CritiqueProduct
Business Facing
Technology Facingfrom Brian Marick
Testing Quadrant

WHICH TESTS DO WE
AUTOMATE?

Functional Tests
Acceptance Tests
Unit Tests
Integration Tests
Component Tests
System Tests
Exploratory Tests
Usability Tests
Performance Tests
Load Tests
Stress Tests
Security Tests
SupportProgramming
CritiqueProduct
Business Facing
Technology Facingfrom Brian Marick
Automated
Automated
Automated
Manual
Testing Quadrant

HOW MANY OF EACH
TYPE?

Business Layer
Web Layer
Browser
Data Layer
CodeCode
Code Code Code Code
Code CodeCodeCode
Code Code Code Code
Database
Unit
Integration
System
Acceptance

Test Coverage
Test Execution Time
Test Feedback
Test Maintenance

Testing Pyramid
Unit Tests
Integration/System
Tests
Functional
& AT Tests
UI
Tests
Manual

WHEN DO WE START
TESTING?

Task Board
To Do In Progress Testing Done
User
Story
User
Story
User
Story
Task Task Task
Task Task
Task Task
Task Task

TESTING IS NOT A
PHASE

Task Board
To Do In Progress Done
User
Story
User
Story
User
Story
Task Task Task
Task Task
Task Task
Task Task

WHO IS DOING THE
TESTING?

TESTING IS
EVERYONE’S
RESPONSIBILITY

Think
Test
Code
Refactor
Test Driven Development (TDD)

HIGH CODE
COVERAGE IS NOT
THE GOAL WITH TDD

Testing Pyramid
Unit Tests
Integration/System
Tests
Functional
Tests
UI
Tests
Manual

DO NOT DO
FUNCTIONAL TESTING
VIA THE UI

As a customer I want to see a running total of
all items in a shopping cart So that I can stay
within my budget.
Running Total

Business Layer
Web Layer
Browser
Data Layer
Code
Code
Code
Code
Database
Code
Code
Code
Code

EXECUTABLE
SPECIFICATION

As a customer I want to collect books in a shopping
cart So that I can order several books at once.
• Books can be added to the shopping basket
• Books can be removed from the shopping basket
• Shopping basket is initially empty
• The same book can be added multiple times to
the shopping basket
User Story

• Requirements and tests are just two sides of
the same coin
– You can’t have a user story (requirement) without
acceptance criteria (test)
• Agile testing focuses on melding requirements
and tests into executable specifications
Executable Specifications

As a customer I want to collect books in a shopping
cart So that I can order several books at once.
• Books can be added to the shopping basket
– Given my shopping basket is empty
– When I add the book “Harry Potter” to my shopping
basket
– Then my shopping basket should contain 1 copy of
“Harry Potter”
Specification by Example

As a potential customer I want to collect books in a
shopping cart So that I can order several books at once.
• The same book can be added multiple times to the
shopping basket
– Given my shopping basket contains 1 copy of “Harry
Potter”
– When I add the book “Harry Potter” to my shopping
basket
– Then my shopping basket should contain 2 copies of
“Harry Potter”
Specification by Example

Green Documents
• Use Specification by Example to create “green documents”
– Less Likely to rot
– Not write once documents
– Help people think and collaborate
– Communicate what the product really does
– Become automated acceptance tests
– Become part of regression test suite

PASS
REFACTOR CODE
FAIL
FAIL
PASS
Automated Acceptance Test Automated Unit Test
User Story
Acceptance Criteria
Back
Acceptance Test Driven
Development (ATDD)

WHAT ABOUT
GREEN FIELD
vs.
LEGACY

Business Layer
Web Layer
Browser
Data Layer
Code
Code
Code
Code
Database
Code
Code
Code
Code Code

USABILITY TESTING

Credit: John Bellomy

EXPLORATORY
TESTING

EXPLORATORY
TESTING IS NOT
AD-HOC TESTING

EXPLORATORY
TESTING IS NOT
EXHUASTIVE
TESTING

Exploratory Testing
• A sophisticated, thoughtful approach to
testing without a script
• Enables going beyond the obvious variations
that have already been tested
• Combines learning, test design and test
execution into one test approach
• Applies heuristics and techniques in a
disciplined way

Session Based Testing
• Time-boxed and structured
• Mission/charter based
• Look for patterns that do not look right
• Divert from the mission if necessary
• Report on your results

SUMMARY
1. Testing in not a phase
2. Testing is everyone’s responsibility
3. Testing starts on day 1
4. Do automate all scripted tests
5. Developers are the one’s doing most of the
automation
6. Do use executable documentation
7. Do not automate functional testing via the UI
8. Save most manual testing for usability and
exploratory testing

REFERENCES

Agile testing - Testing From Day 1

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Agile testing - Testing From Day 1

Similar to Agile testing - Testing From Day 1 (20)

More from Kaizenko

More from Kaizenko (9)

Recently uploaded

Recently uploaded (20)

Agile testing - Testing From Day 1

Editor's Notes