AgileTD: Experimenting in Context for Exploratory Testing

15
Experimenting in Context for Exploratory Testing Maaret Pyhäjärvi Email: <[email protected]> | Twitter: maaretp

Transcript of AgileTD: Experimenting in Context for Exploratory Testing

Page 1: AgileTD: Experimenting in Context for Exploratory Testing

Experimenting in Context for

Exploratory TestingMaaret Pyhäjärvi

Email: <[email protected]> | Twitter: maaretp

Page 2: AgileTD: Experimenting in Context for Exploratory Testing

Replacing a test-case-driven style with a

learning-tester-driven style in

two organizations

Page 3: AgileTD: Experimenting in Context for Exploratory Testing

What Testing Gives UsUn

it Te

stin

g

Expl

orat

ory

Test

ing

SPECFEEDBACKREGRESSIONGRANULARITY

GUIDANCEUNDERSTANDING

MODELSSERENDIPITYTesting as

artifact creation

Testing as performan

ce

Page 4: AgileTD: Experimenting in Context for Exploratory Testing

Givens. Some things you can’t change (yet)

Page 5: AgileTD: Experimenting in Context for Exploratory Testing

Experiments. Try changing something!

Page 6: AgileTD: Experimenting in Context for Exploratory Testing

Finding the appropriate stretch

Case 1.

Page 7: AgileTD: Experimenting in Context for Exploratory Testing

Data-intensive application

Page 8: AgileTD: Experimenting in Context for Exploratory Testing

Givens. Things I could not change.

• Waterfall process. • Contractual distance between

acceptance testers and subcontractor.

• Test-case metric based reporting.• I manage, I don’t test. • Business end users as testers.

Page 9: AgileTD: Experimenting in Context for Exploratory Testing

Experiments. Things I changed.• Acceptance tester degree of

freedom.• Test cases from step-by-step scripts

to test data with process outline for notes.

• Making “change requests” acceptable.

• Reporting ~20% of testing to 3rd party.

• Inofficial tips sharing sessions with the subcontractor.

Page 10: AgileTD: Experimenting in Context for Exploratory Testing

Finding the appropriate stretch

Case II.

Page 11: AgileTD: Experimenting in Context for Exploratory Testing

Function-intensive application

Page 12: AgileTD: Experimenting in Context for Exploratory Testing

Givens. Things I could not change.

• Roadmapping creating disconnect to current priorities.

• Tendency for remote work.• Developers doing majority of testing. • Requirements / Specifications format

as UI spec

Page 13: AgileTD: Experimenting in Context for Exploratory Testing

Experiments. Things I changed.• No test cases or wasteful

documentation.• Tester with developer tools. • Removing “acceptance testing” by

moving testing to the team.• Continuous delivery (without test

automation).• Holding space for testing to happen. • True teamwork with mob programming.

Page 14: AgileTD: Experimenting in Context for Exploratory Testing

Framework of Management

”A day’s work”

Vision (“Sandbox”) Current Charter

Other Charters Details

Bug Reports

Perception of quality

and coverage

Quality ReportDebriefin

g

Tester

Test Manager

PastResultsObstaclesOutlookFeelings

?#

xCharter backlog of the future testing

Out of budget

Next in importanc

e!#, ?, x, +20:20:60

Session sheets of the past testing

Idea of explorati

on

Metrics summa

ry

Coaching

Playbooks

Page 15: AgileTD: Experimenting in Context for Exploratory Testing

Thank you.

@maaretp(please connect with me

through Twitter or LinkedIn)