Agile ALM and Testing

Getting testing done in a sprint

Clemens Reijnen

clemens.reijnen@sogeti.nl

www.clemensreijnen.nl

@clemensreijnen

www.youtube.com/clemensreijnen

www.slideshare.net/clemensreijnen

Agile ALM and Testing

an iterative, incremental approach to optimize predictability and control risk.

work together__with work packages__on alm artifacts

http://www.gartner.com/technology/reprints.do?id=1-1ASCXON&ct=120606&st=sb

Driven by cloud and agile technologies, the ALM market is evolving and expanding. Although support for agile is important, the challenge is that the tools that work best for agile projects lack requirements definitions and management.

Magic Quadrant for Application Life Cycle Management

Agile ALM and Testing

work together connected with ALM tools to deliver a done increment within iteration

Getting Testing Done in a Sprint

10 TIPS

get a Team

1

backlog items need a risk

classification

2

Product Backlog items have the attributes of a description, priority, and estimate. Priority is driven by risk, value, and necessity. There are many techniques for assessing these attributes.http://www.scrum.org/scrumguides/

“no risk, no test”

create logical test cases

during release planning meeting

3

define test tasks during

sprint planning meeting

4

team focus on a product

backlog item

5

undone work

6

DEMO

automation is a must, but

not everything

7

TIP for get testing done in a sprintTest Automation Levels0

1

2

3

4

No automation

Shared Steps with action recordingTest Cases with action recordingGenerated Coded UI

Customized Coded UI

Test Automation Levels

Number of test cases per level in a sprint.

Test

Case

s w

ith a

ctio

n

reco

rdin

g

Genera

ted C

oded U

I

Share

d S

teps

wit

h a

ctio

n r

eco

rdin

g

Cus

tom

ized

C

oded

UI

No

auto

mat

ion

No Double, Triple Testing

8

The Test Branch

9

BUGS

10

DEMO

DONE

www.ClemensReijnen.nl

@ClemensReijnen