2. Product
Release
User story
Task
Planning : Product –> Release -> Iteration –> User stories - > Tasks testing
User story
User story
Task
Task
Task
Task
Task
Task
Task
Task
Detailed planningHigh level planning
3. Product
Release
User story
Task
High level planning :
Sprint 0
Approach
Scope
Functional tractability to
tests
Planning /performing :
Acceptance test
Functional tests
Regression
Mini hardening!?
i
n
t
e
g
r
a
t
i
o
n
Unit tests
Peering
[Development environment
tests]
Planning : Product –> release -> iteration –> user stories - > Tasks testing
17. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering with
developer (per task/s)–
understanding the
development approach
Task
Automating
tests
Working software
Test early!
Acceptance
criteria
18. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering
with developer (per
task/s)– understanding
the development
approach
Task
Coding
(with tdd)
Automating
tests
Working software
Test early!
Acceptance
criteria
19. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering with developer
(per task/s)– understanding the
development approach
Task
coding
Unit testing
execution
Automating
tests
Working software
Test early!
Acceptance
criteria
20. User
story
Task
ATDD
Planning
functional tests ,
regression ,
integration
,customer ?tests?
other tests
Testers are Peering with
developer (per task/s)–
understanding the development
approach
Task
coding
Unit testing
execution
Peering – Testing on
development environment
(automation or manual)
Automating
tests
Working software
Test early!
Acceptance
criteria
21. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering with
developer (per task/s)–
understanding the development
approach
Task
coding
Unit testing
execution
Peering – Testing on
development environment
Automating
tests
Working software
Test early!
Acceptance
criteria
22. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering with
developer (per task/s)–
understanding the
development approach
Task
coding
Unit testing
execution
Peering – Testing on
development environment
Automating
tests
Unit tests pass
Working software
Test early!
Acceptance
criteria
23. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering with
developer (per task/s)–
understanding the
development approach
Task
coding
Unit testing
execution
Peering – Testing on
development environment
Functional,
(exploratory)
Performing/ automation
Acceptance (and with PO).
Regression
Defining mini hardening
Automating
tests
Unit tests pass
Working software
Test early!
Acceptance
criteria
24. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering with
developer (per task/s)–
understanding the
development approach
Task
coding
Unit testing
execution
Peering – Testing on
development environment
Functional,
(exploratory)
Performing/ automation
Acceptance (and with
PO).
Regression
Defining mini hardening
Automating
tests
Unit tests pass
Working software
Test early!
Acceptance
criteria
25. User story
Task
ATDD
Planning functional
tests , regression ,
integration ,customer
?tests? other tests
Testers are Peering with
developer (per task/s)–
understanding the
development approach
Task
coding
Unit testing
execution
Peering – Testing on
development environment
Functional,
(exploratory)
Performing/ automation
Acceptance (and with
PO).
Regression
Defining mini hardening
Automating
tests
Unit tests pass
Working software
Test early!
Acceptance
criteria
27. » Making sure a functional area is stable – working
software
» Few hours to 1-2 days - top
» Taking a group of user stories (keep it small and simple)
» Stop
» Perform related regression
» Perform short exploratory
» Automation regression reduce the need of mini
hardenings.
29. Unit Test Every piece of code Continuous on every
peace of code
Acceptance tests Business related Every user story , and
on every Build
Integration Test Continuous Integrated system|
(Server, DB etc). execute
automation regression , End to
end flow for each functional
unit.
Daily
End 2 End Integrated system against live
product
Nightly / Weekly/Build
30. Type Measurements
Sanity Integration After each build creation ,
to have 100% passed sanity
scenarios
End 2 End
Regression Integration
Measure Success rate.
End 2 End
Manual
Progression Acceptance
Measure Success rate.
Integration
End 2 End
Manual
Load Integrated system List of end to end flows
and covered scenarios
results
Stress Integrated system
