Agile testing

Agile Testing Elhanan Rosental – Matrix Global Agile Leader

• Agile is perfect for Israelis

• No Documentation

• Do Whatever feels good

• Code to the last moment

• Compressed schedule

Is that right?

Some Agile myths

• Agile is not sloppy coding but a very

disciplined

• That means that some teams are not agile but

just sloppy

• Being Israeli doesn’t mean you are Agile

Wrong!!!

• Every iteration is a shippable product

• Every iteration Must be tested

• “Done” is not done without testing

Potential Shippable Product

• Sprint Planning

• Beginning of the sprint

• During the sprint

• Toward the sprint end

• Retrospective

Tester Lifecycle in a sprint

• The Tester is full part of the team

• He estimates the developers tasks as well

• His insight is very valuable as he think “out of

the box”

Sprint Planning

• The tester and developer sits together to make

sure that they understand the user story the

same way

• In any disagreements the PO will be asked to

make sure that everything is clear

• Developer start develop, Tester starts design

the test.

Beginning of the sprint

• Agile encourage just enough documents

• There is no need to spend time of formal STD

• The test should be designed with the correct

clarity

Is there a need for STD?

• Testing is done all the time!!

• We are not waiting to the development finish

• Every time there is something done the tester

should test it and give insight.

During the sprint

Testing is not a phase!

http://testobsessed.com/wp-content/uploads/2011/04/AgileTestingOverview.pdf

• Toward the sprint end the developer should

finish the task

• The tester should run final overall test

• The developer should concentrate on bug fix

and closing the task

Toward the sprint end

• Understand the bugs idea

• Bugs are not Product

• In what cases should a bug opened

• When should a bug opened

Should the tester open bugs?

• Tester is part of the team

• Retrospective should refer to the points:

• Cooperation in the team

• Did the tester get the task with enough time to test?

• Cooperation with the other stakeholders

Retrospective

• Don’t let the bug number grow. Handle them

while the number is small

• Are there bugs that we shouldn’t treat?

• Can sprint requirements be considered “done”

with bug hanging around?

Bug Handling

• Is there a need for an independent system test

QA team?

System tests

• Testing for overall flows that were created

over the sprints

• Acceptance before version release

• In case of a outsource team important for the

customer confidence

Reasons for a system QA team

• Every Sprint we should deliver Potential

shippable product

• Shippable product mean that all the system is

tested for regression

• After some sprints it is impossible to be done

manually

Some thoughts

• Automation testing can save a lot of repeatable

testing

• We should aim toward as much automation as

possible

• Automation needs a maintenance

The solution: Automation Testing

• Create Automation

backlog tasks

• Prioritize tasks

by 3 factors

Balance Automation

• No!!! Every body is responsible for working

product

• Tester added value is his experience and

expertise

Is the tester the only one testing

• Unit Testing

• TDD- Test Driven Development

• Tester and developer can work in TDD. Write

tests before start developing!

Developer Testing

Questions?