Embed Size (px)
Citation preview
• Involved in development of core Atlassian products
• Commercial, Open-Source add-ons, customizations
• Developers, Product Managers, Designers, QAs, Agile Team Leads
• QA for Quality Assistance
Partner
My Agile story
2006
• My first real Agile Project
• Heard about Agile in 2006 on ISTQB straining
• First project - 2006
• No one knew what to do
• Testers in Agile? No experiences available
• Short story
2012
2013
• Quality Assistance
“There are now many teams that label themselves as ‘agile’, but some agile teams are more agile than others”
Stuart Reid “Are all pigs equal?” Testing Experience 2009
My first "Agile" project• Test Manager
• Around 10 developers at the beginning, 3 testers
• No shared quality responsibility, bad fitting, technical debt
• No experience, no enough thinking, no guidance
TOAST FOR QUALITY
QUALITY ASSISTANCE
TOAST 4 QASSISTANCE
5 FAQs
• Tomek: Ale nasypało, motyla noga! Już od kwadransa nie ma autobusu! Kurcze pióro!
• Dziewczynka: Nie do wiary! Jak można się tak brzydko wyrażać?!
• Tomek: A co mam mówić?! Jak mi nogi zmarzły... Motyla noga…
• ??????: kiedy następnym razem znów wyłączą wam ciepłą wodę, przestaną grzać kaloryfery, albo stanie komunikacja i wasz kolega znów zacznie mówić brzydkie wyrazy, udawajcie, że nie słyszycie, co do Was mówi. Że nic nie słyszycie.
WUJEK DOBRA RADA
Dziewczynka: To jest wspaniała rada! Chłopiec: Pycha!Chłopiec II: Wyobrażam sobie jego minę!
QA
TOAST FOR QUALITY
TT0ASSS
Types and Techniques
Organization
Added value
Skills
Tracking
Set the base for your QA process
Strengthen the base with organization
Do you have skills to fill the bowl?
Make a place for your drink
Do you know how to taste your
drink?
TOAST for Quality
• A model helping to organize QA process inside Agile project
• Refers to whole quality process - not only QAs
T - Types and Techniques
O - Organization
A - Added value
S - Skills
T - TrackingT0
AS TSS
Types and Techniques
• Which test types do you need to execute within your Agile process?
• Which software characteristics you need to cover (performance, usability)?
• What techniques will you use for those tests?T0
AS TSS
• Types:
• Functional tests, Performance, Load, Stress, Usability, …
• Techniques:
• Scripted testing, Automated tests, Exploratory testing
• White-box, Grey-box, Black-box
Types and Techniques
Agile Te
stin
g
Quadr
ants
T0
AS TSS
…
…
…
TO
PR
OD
UC
TIO
Nand TimingT0
AS TSS
…
…
…
STORY TESTING
FEATURE REGRESSION
PRODUCT REGRESSION
FEATURE TESTING
PRODUCT REGRESSION
RELEASE TESTING
PRODUCT REGRESSION
and TimingT0
AS TSS
• How do you plan to organize testing activities?
• Quality is the responsibility of the complete team!
• What is the team setup (How many QAs? How many Developers)?
• What is the QA role in testing activities?
OrganizationT0
AS TSS
TA
0S TSS
• Where do QAs add value beyond testing? Do we test at all?
• Automation, Business Analysis, Acceptance Criteria, Customer Support, Customer Contact, Test Data, Test Environments?
Added ValueT0
AS TSS
T0S TASS
• The team must feel QA is mandatory element of the team and its every activity
• Get the unique strengths and use them
Added ValueT0
AS TSS
T0S TASS
TDD, BDD, ATDD
• Visibility of QAs work!
• “Yesterday testing, today testing”
• Daily stand-ups
• Interesting idea:
• ‘Report on your product’s health’ by Henrik Andersson
(http://tvfortesters.com/video/adding-value-in-an-agile-context-by-henrik-andersson/)
QA Dobra Rada#1
• What skills do we need in the team?
• What do we need to do to fulfil needs?
• Where can QAs specialize?
• Are QAs technical enough?
SkillsT0
AS TSS
T0
AS SS T
• How do we estimate QA activities and verify those?
• How do we measure the process?
• How do we measure product quality?
• How do we get inputs for retrospective?
TrackingT0
AS TSS
T0
AS TSS
• QA Tasks tracking
• Internal and External product quality
• Dev speed, QA speed
• Product health
• Product usage
TrackingT0
AS TSS
T0
AS TSS
T0
AS TSS
QUALITY ASSISTANCE
Strategy
• The ability to test is not some magical genetic trait, but a skill that can be taught and learned
Strategy
• Developers that master testing not only increase the efficiency and capacity of their teams, but also write higher quality software.
Strategy
• When testing can be confidently shared with developers, the people who are passionate about quality, such as great testers, can focus on solving the root causes of quality problems in addition to discovering their symptoms.
to
QA
1 x 10
TESTERS QASSISTANTS
Metaphor
● Process improvement
● Test tools, test environments
● Customer insight
● Prevention, data-driven decisions, quality education
Those other things
TOAST 4 QUALITY ASSISTANCE
Types
• Functional testing incl. security
• Performance
• Usability
T0
AS TSS
Functionality:
• Automated testing
• White-box static testing
• Grey-box manual exploratory testing
Techniques
Unit Tests
Func tests
UI
AT MT
T0
AS TSS
Exploratory
Don’t think “does it work?”Think:
“When shouldn’t it work?”“When mightn’t it work?
T0
AS TSS
QA Dobra Rada
• We do not know how to describe the exploratory thinking
• Considered as ‘playing around’ without any test documentation
• Fight that!
• Think about it before encouraging your organization
#2
…
…
…
STORY TESTING
FEATURE REGRESSION
PRODUCT REGRESSION
FEATURE TESTING
PRODUCT REGRESSION
RELEASE TESTING
PRODUCT REGRESSION
TimingT0
AS TSS
Release every 2 weeks
FEATURES STORIES
Release 2-3 times a year
FEATURES STORIES
Testing
STORY TESTING FEATURE REGRESSION
PRODUCT REGRESSION
FEATURE TESTINGPRODUCT
REGRESSION
RELEASE TESTINGPRODUCT
REGRESSION
Story
Feature
Release
Autom. (CI) Autom. (CI)
Autom. (CI)
Autom. (CI)
Manual exploratory tests+ Automated tests
(Optional) Blitz Test
NO
T0
AS TSS
QA Dobra Rada
2, 3 times a year….before delivery…..
every two weeks ….
but later ….
#3
Ship often!
Quality Assistance
• 1 QA per 10 developers
• Testing in hands of developers (both manual and automatic)
• Teaching, coaching
• Process improvement, experimenting, bugs analysis, test tools
TA
0
S TSS
Our story• All tests by
Devs
Coding Done
TA
0
S TSS
STEP 1
Our story• All tests by
Devs
Coding Done
• QAs Testing
Testing
TA
0
S TSS
STEP 2
Our story• All tests by
Devs
Coding Done
• QAs Testing
DoTing• DoTing
TA
0
S TSS
STEP 3
Our story• All tests by
Devs
Demo Done
• QAs Testing
DoTing• DoTing
• QA Demo
Coding
TA
0
S TSS
STEP 4
Our story• All tests by
Devs
Coding DoTing
• QAs Testing
Demo• DoTing
• QA Demo
Kick-off
• Kick-off
Done
TA
0
S TSS
STEP 5
Our story• All tests by
Devs
Kick-off Demo
• QAs Testing
Coding/Testing
• DoTing
• QA Demo
Review
• Kick-off
Done
• TNs reviewTA
0
S TSS
STEP 6
Kick-off DemoCoding/Testing
Review
Done
Testing Notes
Risky scenarios
Fit for exploration
Written by Developers, reviewed by QAsTA
0
S TSS Current state
QA Demo
Not test session
Gain QA confidence
Assess if more tests are necessary
Kick-off DemoCoding/Testing
Review
Done
TA
0
S TSS Current state
Blitz testing• Complete team
• Goal-focused or open
• 1-2 hrs session
• Finalized with bug triaging
• Used by some teams to validate QA process - Is it?
TA
0
S TSS
• Teaching / mentoring
• Test tooling, test coverage
• Process improvement, bug analysis
• We are “linkers” and “sharers”
• Customer view
Added valueT0
S TASS
QA Dobra RadaExperiment Take risks
Process Product&
#4
Does this sound familiar?
• QA must limit the speed, QA must hold development plans, QA must make sure we do not take risks
Teaching/mentoringT0
S TASS
Assistance skills• Experienced tester
• Soft-skills
• Change agent
• Mindset - solve symptoms not problems
• Thought leader
T0
AS SS T
• Technical knowledge regarding web-application risks
• Test automation knowledge
• Finding risks in the code - White-box testing
• Developing simple testing tools
Technical skillsT0
AS SS T
• Go beyond!
• Find opportunities
• Develop new skills
• Create new added value
QA Dobra Rada#5
• Story rejection rate, internal bugs per story
• OD Incidents, Stable regressions
• Process metrics
What do we track?T0
AS TSS
Do we do that?
• Not much people sharing it
• Stay tuned
T0
AS TSS
5 FAQs
Does it work?
Challenges
• Rapid team growth
• Increasing complexity of products, source code and test code
• Old tests, too many tests, flakey tests
• Product scalability
Isn’t it expensive?
• Building quality into the product vs. Testing quality into the product
• Build - Test - Build - Test - …
• No objective measures
Where to start?
• Quality responsibility
• Exploratory testing
• Process improvement
How can you coach if you do not test?
• Isn’t finding risks testing? We do test!
• Your knowledge about the product increases much faster, your risks register is much broader
• You are much closer to the code and get better in white-box testing
• You learn a lot more
SUMMARY
Think if you merit a TOAST
Think of having QAssistance
Think of becoming QAssistant
The train is leaving• Development specificity
changes
• QA specificity changes:
• Analytics, Experiments, A/B Testing, Continuous Deployment
• Explore new paths!
Thank you!
WE’RE HIRING!spartez.com/career
Images - credits• Żuraw in Gdańsk - by JM_GD - CC BY 2.0
• 3D Growth Projections - by Chris Potter - CC BY 2.0
• Architetto -- Donna casinista - by francesco_rollandin - CC BY 2.0
• Animal farm - by newtown graffiti - CC BY 2.0
• Toast - by Stiefen Schlingen - CC BY 2.0
• Toasting Champagne - Waldo Jaquith - CC BY-SA 2.0
• Thinking - by Wade M - CC BY-SA 2.0
• Stadion Narodowy w Warszawie - by Artur Malinowski - CC BY 2.0
• Calling for Backup - by myfuture.com - CC BY-ND 2.0
• Listen, Don’t Talk - by U.S. National Archives and Records Administration - CC BY 2.0
• Atomic Laboratory Experiment on Atomic Materials by NASA/Paul Riedel - CC BY 2.0
• Alarm Building Fire - by Keener, Jo L. - CC0 1.0
• Surprise!! - by Benson Kua - CC BY-SA 2.0
• Green fields in Gramado - by Anne Valladares - CC0 1.0
• Freedom - by lholtz1023 - CC0 1.0
• Toast to 2012 - Hakee Chang - CC BY 2.0
• Train Left - SElefant - CC-BY-SA-3.0
• Steps - Derek Adkins - CC-BY-SA-2.0
• POL Miś Bemowo - by Hiuppo - CC-BY-SA-3.0
• Raise_your_hand_if_you_can’t_swim - by National Photo Company - CC0
1.0
• Miss Dee Dee by pixiemotionpotion - CC-BY-SA 3.0
• Wembley - by Lewis Clarke - CC BY-SA 2.0
• Thumbup - Pratheepps - CC0 1.0
• Documentation - by Marta Pucciarelli - CC-BY-SA-3.0
• Difficult - Sea Turtle - CC BY-NC-ND 2.0
• Chemia Laboratorium Experyment - pixabay.com - CC0 1.0
• Comic Daredevil Bello Nock - Chris Phutully - CC BY 2.0
• Surprise major - by Achim Hering - CC-BY-SA-3.0
• Train Left - SElefant - CC-BY-SA-3.0
• Intel trucks – by Ryan Holst – CC-BY 2.0
