KUADRIGAVladimir Primakov

Test management in SCRUM:Main testing

documentation/artifacts, tools, approach to test management

Vladimir Primakov

QA manager and Automator with 9 years experience in software testing.

The main current activity: Evaluation and startup of new software testing projects, testing processes and infrastructure setup, test management in the Kuadriga company.

Enjoy photography, sports, and self-improvement

Profile in Linkedin: http://www.linkedin.com/in/vladimirprimakovEmail: v.v.primakov@gmail.comSkype: vladimir.primakov

Test Basis

Testing Artifacts/Documents/Tools

Test Basis

Vision User stories, epics

Architecture

Sprint/Milestone backlog

WorkflowsOld ProductPrototypes

Testing/QC Documentation/Artifacts

?

Testing/QC Documentation/Artifacts

Test Strategy Testing Sprint Plan Test Case Test Suite Script (Suite)

Defect Report Quality Report Dev. Infrastructure Auto Test Policy

Main Testing Artifacts

Test Strategy Test Sprint Plan Test Case Test Suite

Defect Report Quality Report Dev. Infrastructure

Testing Artifacts to Discuss

Test Strategy Test Sprint Plan Test Suite

Quality Report

Master Test plan \ Testing Strategy

Master Test plan \ Testing StrategyProducts, their parts Technologies, and Tools Test Environments Testing types

Testing & Dev. Integration Product & Project risks Team Initial Schedule

Planning Testing Sprint

&

Planning Testing Sprint

Dev. Sprint

Planning Testing Sprint

Dev. Sprint QA Sprint

Planning Testing Sprint

Dev. Sprint

User story

QA Sprint

Planning Testing Sprint

Dev. Sprint

User story

QA Sprint

Planning Testing Sprint

Dev. Sprint

User story QA Task

QA Sprint

Planning Testing Sprint

User story QA Task

Planning Testing Sprint

User story QA Task

Link with the field

Note: A field of the Label type

Planning Testing Sprint

User story

QA Task

Planning Testing Sprint

User story

QA Task

Estimate!

Planning Testing Sprint

User story

QA Task

Estimate!

Planning Testing Sprint

QA Task

QA Sprint

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available(e.g.: Test planningTest reporting, etc.)

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

QA Sprint

Create andAdd to sprint

Time Estimated < Time Available

Planning Testing Sprint

Time Estimated > Time Available

Planning Testing Sprint

QA Sprint

Time Estimated > Time Available

Planning Testing Sprint

But

Planning Testing Sprint

is Obligatory!

Planning Testing Sprint

Exploratory testingSession-based testingError GuessingExperience-based testingAd Hoc testingSmoke testing

=

Planning Testing Sprint

QA Task Tester

Dividing tasks

amongTesters

Пока Вы спите кто-то может забрать вашу прелесть

Regression (Test Suite)

Regression (Test Suite)

MonitoringTracking testing by a whole team

MonitoringTracking testing by a QA Manager

MonitoringTracking testing by a QA Manager

Burndown and project summary

MonitoringTracking testing by a QA Manager

Regression Test coverage

Time Spent by certain testers

Может Хватит!?

Может Хватит!?

Да, блин, ещё чуть, чуть!...

Reporting

1. Defects by severity/priority (and their status)

Reporting

2. Defect distribution by components (and their status)

Reporting

3. List of bugs that perceived to be obligatory fixed before release.4. List of bugs recommended to be fixed before release.

Key Summary Assignee Priority StatusID-535 Bla-bla-bl-bla-bla-bla-bla-bla-bla-bla-bla-bla-

bla-bla-bla-bla-blBruce Lee Urgent Open

ID-525 Bla-bla-bl-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla

Bruce Lee Major Open

ID-440 Bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bl

Bruce Lee Normal Resolved

ID-150 Bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla

Batman Normal Resolved

Reporting

5. Regression test coverage

Reporting

6. Test deepness for user stories or regression test cases:

• Very thought out detailed tests• Detailed tests• Deep smoke test• Smoke test• Nothing

7. Obligatory Types of Testing performed / not performed 8. Obligatory Test Environments covered / not covered

Documentation Storage

Versioning backup

Shar

ed F

olde

r

Use Templates!

Vladimir Primakov

Email: v.v.primakov@gmail.com

Skype: vladimir.primakov