How To Manage Testing
in Dynamic World
@adzyniav 1.1.2
?
Idea
Minimal Valuable
Product
GO
LIVE
AND ?
@adzynia
Fixing bugs Missing features Angry Users Lack of time
Stress
QA
!
be Responsible for Quality
Write test plan
write test cases
do manual testing
automate testing
To
To Do In Development Code Review Testing Demo
! User Story
User Story
User Story
User Story
User Story
User Story
User Story
2 Days Before Demo
@adzynia
Outsource testing?
Oh no...How it can be different?
QA != TestingQuality is whole team responsibility
BA Dev Tester
User Story
Look for consensus! not compromise
WIN/WIN!WIN/lose
lose/WINlose/lose
3 Amigo’s Meeting
Tester
Business
Developer
Acceptance Scenarios Testing Checklist Testability Tasks
Outcome
Scenarios Demohttps://github.com/adzynia/cucumber-jvm-scrum-test
@adzynia
Manual Testing Is
Still Important !
But
Checking != Testing
@michaelbolton
Session Based Test Management
VS Test Cases Management
Testing Session
should be:Goal focused Time-boxed Reported Debriefed
Learning
Design
Execution
Feedback
Exploratory testing
@jamesmarcusbach
?
Regression Testing
Functional Map
MOdel based testing?
to be continued…
Release to
Productionshould be
EASY
At the End you will getFriendly Team
Living Documentation Automated Acceptance Scenarios
Functional Map Testing Session Reports
Stable Delivery Pipeline
To Do Acceptance Test Design In Development Code Review Testing Demo
! User Story
User Story
User Story
User Story
User Story
User Story
User Story
Development flow
User Story
@adzynia
AND Do not forget about Balance
Control Ad-hoc
To Read
