Testing in SCRUM Scrum Meet up Colombo December

Testing in SCRUM Scrum Meet up – Colombo – December 2015 Hirantha Wanasundara

Why testing is important?

Testing is not just finding bugs…. . It is the systematic assessment of an application’s fitness for the purpose it has been designed for

Clients do not want a costly and stressful problem with software; • that doesn't work • isn't ready on time • does not meet specifications • impacts customers adversely • has bugs • is too complicated to use

Testing should be conducted throughout the lifecycle for maximum project benefit

Traditional Vs. Agile testing

Strict change management over Change is inevitable

Comprehensive documentation over Working software

Up front planning over Plan to the next iteration

Formal entrance and exit criteria with signoffs over Collaborate, don’t hand off

Comprehensive system-level regression tests over Detect defects earlier with automated unit tests and continuous integration

Common test approach for SCRUM

Agile testing principles

1. Testing moves project forward

2. Testing is not a phase

3. Everybody tests… not only designated testers

4. Reduce feedback latency

5. Tests represent expectations

6. Clear bugs without piling up

7. Reduce test documentation overhead

8. Complete testing is part of “Done”

9. From test last to test driven development

Agile testing best practices

1. Test driven development (TDD)

TDD cont…

Week 1 M Tu W Th Pre Sprint Week 2 F M Tu W Week 3 Th F M Tu W Target Sprint UAT regression testing Sign-off Smoke test and client demo Development and testing in parallel Test automation UAT planning meeting Pre planning meeting Acceptance test case writing TDD cont… Week 4 Th F M Tu W Th Post Sprint F

2. Continuous Integration (CI) & Automation

CI & Automation cont…

3. Exploratory testing and Defect Driven Testing (DDT)

4. Risk and value based testing

5. Clear definition of “Done”

6. Collaboration with team and stakeholders

7. Team work and mindset change