helpful practices in agile testing

W4 Agile Testing 5/4/16 11:30

Helpful Practices in Agile Testing

Presented by:

Jeroen Mengerink

Polteq Testing Services B.V.

Brought to you by:

350 Corporate Way, Suite 400, Orange Park, FL 32073 888-‐-‐-‐268-‐-‐-‐8770 ·∙·∙ 904-‐-‐-‐278-‐-‐-‐0524 -‐ [email protected] -‐ http://www.stareast.techwell.com/

Jeroen Mengerink Polteq Testing Services B.V. Test consultant for the Netherlands-‐based Polteq Test Services B.V. Jeroen Mengerink has performed multiple TPI assessments worldwide. His technical skills allow him to team with developers in testing websites, APIs, and web services. Jeroen performs both functional testing and performance testing. In addition to his work for clients, he is involved with test innovations in agile. Jeroen teaches the Certified Agile Tester course and courses on agile, SOA, and cloud; coauthored Testing Cloud Services; and blogs at jmengerink.wordpress.com. Follow him on Twitter @AngusVB.

Helpful Practices in Agile Testing

Jeroen Mengerink [email protected]

2 © 2016

What is agile?

agile /’æd3aIl; NAmE ’æd3l/ adj. 1 able to move quickly and easily SYN nimble: a strong and agile athlete 2 able to think quickly and in an intelligent way: an agile mind / brain (source: Oxford Advanced Learner’s dictionary)

3 © 2016

Transitioning from traditional to agile

Process Waterfall Development

Transition Agile Development

Measure of Success

Management Culture

Requirements & Design

Coding & Implementation

Test & Quality Assurance

Planning & Scheduling

Conformance to plan

Response to change, working code

Command & control

Leadership, self managing teams

Big & upfront documentation

Continuous, just in time elaboration

Code all features in parallel. Test later

Code & unit test, deliver serially

Big, planned / test late Continuous & concurrent testing starts early

detailed / fixed scope, estimate time & resources

Two-level plan / fix date, estimate scope

(Scaling Software Agility: Best Practices for large Organisations – DeanLeffingwell 2007)

4 © 2016

Evolution of agile testing

Pioneering

Structured

Agile

Time

Str

uctu

red

N

ot

str

uctu

red

5 © 2016

Agile testing

• More focus on soft skills

• Technical aspects (drivers, stubs, logging, …) are part of the job

• Share test knowledge

– Within profession, over teams

– Within team, over professions

• It is more than just testing

6 © 2016

Teamwork

• Respect and trust each other

• Commitment as a team

– Work towards a team goal

• Help each other where possible

– Multi disciplined

7 © 2016

Visualize the goals

8 © 2016

Think about team development

(Bruce W. Tuckman – Stages of group development)

9 © 2016

Make use of T-shaping

• Know the context

• Know your own strengths

• Assist others

• Leave your comfort zone

9

10 © 2016

Pair with other team members

• Introduce boundary value testing to developers

• Introduce what-if thinking to designers

• Suggest scenarios to the product owner

11 © 2016

Agile test management leadership

• People management

• Generic test approach / strategy

• Risk analysis

• Release planning

• Keep the big picture (birds eye view)

– Cross teams

– Cross sprints

– Cross projects

12 © 2016

Define a generic test approach / strategy

• What and when to test?

• Testing is fully integrated in the software development process

• Everybody tests

13 © 2016

Generic test approach / strategy

Define a generic test approach / strategy

Risks Maturity

Skills Product

Size Time

Culture

Bandw

idth

14 © 2016

Large in scope, small in numbers, low code coverage

Small in scope, large in numbers, high code coverage

Test/check at different levels

15 © 2016

Perform product risk assessments

• For the complete product end-to-end (E2E) risks

– Stakeholders, management, and SMEs

• For a release feature/epic risks for that release

– Selection of team members, product owner, and SMEs

• For user stories specific risks for that story

– Team and product owner

Each level has its own type of risks

16 © 2016

Communicate risks

Core

Layer 1

Layer 2 Core: Technical: - Database interaction - Most used DLL’s

Functional: - Most important proces - Most used functionality

Impact : Huge

Core

17 © 2016

Communicate risks

Core

Layer 2 Center layer(s): Technical: - Algorithms - APIs

Functional: - Often used processes - Important functionality

Impact : Middle

Core

Layer1

18 © 2016

Communicate risks

Core

Layer 1

Layer 2

Impact : Small

Outer layer(s): Technical: - Screens / fields - Views - Forms

Functional: - Little used processes - Less used functionality Core

19 © 2016

Don’t forget end-to-end testing

• Focus is wider than current sprint

– Probably wider than the team

• Assign what and when to test

• Make sure to address business value

21 © 2016

Monitor your testing in agile

• Make sure to find out where you are and where you want to go

Key area Forming Norming Performing

1 Stakeholder commitment

2 Planning & Estimation

3 People

4 Interaction

5 Teamwork

6 Test process

7 Test management

8 Test profession

9 Test automation

10 Regression & E2E testing

11 Defect management

12 Test environment