Cross Team Testing is a way to tackle bias. Having testers in the development teams have many benefits but also new challenges. One of these challenges are that the testers get biased. Cross Team Testing is a structured way to tackle this bias. This is my presentation on this subject from DevLin March 14 2013.
3. 18 years in the software business
Developer, Tester, Transport,
Project Manager, Bank&Finance,
Test Manager, Telecom and
Support Manager, MedTech.
Operations Manager,
Quality Manager,
Line Manager...
EAST: Östergötlands Association for Software Testers
Currently: Chief Quality Officer at Sectra Medical Systems
4. Agenda
1. Background & Context
2. Benefits (testers in dev teams)
3. Challenges (testers in dev teams)
4. Cross Team Testing
5. Summary
5. Please note:
Cross Team Testing
Not a ”best practice”
Not a ”universal solution”
Our current practice / solution
for us in our context
11. Benefits
with having testers in the development teams
Early involvement Less admin
Bug prevention Better quality
Easier to make a difference
No wall between test & development
12. Challenges
with having testers in the development teams
Biased (testing your own baby)
Less curious
Walls between the teams
(i.e. between the testers)
20. Planning (2 hours)
1. High level presentation of test objects
2. Planning sessions in smaller groups
21. 2. Planning session in small groups
a. Detailed presentation of the test object
b. Brainstorm test ideas, based on aspects
requested by the Test Owner, such as:
• Coverage criteria
• Quality characteristics (security, stability, …)
• Risks (business, technical, patient)
• Test techniques, test tools, test data
• ...or any other basis or source for test ideas
c. Create test charters (approximately 3-9)
22. 2. Planning session in small groups
a. Detailed presentation of the test object
b. Brainstorm test ideas
c. Create test charters (approximately 3-9)
• Title - Briefly identifies and describes the test idea
and/or mission in one or two sentences
• Test Area - Details any particular focus area of the test
object where the Test Owner would like the testers to
spend most of their session time
• Guidelines Quality characteristics (safety, security,
performance, reliability, capability, usability…).
Oracles (requirements, standards, design consistency…)
Resources (tools, data, test technique, configuration…)
23. Testing (1 day)
• Exploratory group testing sessions (*3)
• Debrief to the Test Owner
• Bug reporting
24. Time Slot Activity
9:20 Test Session #1 70min
10:30 Debreifing Session #1 15min
10:45 FIKA
11:00 Test Session #2 75min
12:15 Debreifing Session #2 15min
12:30 LUNCH
13:30 Test Session #3 75min
14:45 Debreifing Session #3 15min
15:00 -> Bug Reporting / Optional more testing