1 of 47

Creating Test Strategies Teams Will Read

Thomas Shipley - @tomdrivendev

2 of 47

Hi, I’m Thomas 😀

<--- I share ideas at

http://tomdriven.dev

​

<--- and work for ECS. Current project at HSBC

https://ecs.co.uk/

​

<-- sometimes tweet @tomdrivendev

​

3 of 47

A Tale of Two Extremes

4 of 47

Extreme No. 1

  • 100 Pages Long
  • ISO Compliant
  • Written by Committee

Extreme No. 2

  • 1 Side of A4 (maybe)
  • The Test Pyramid
  • Written by Tom

5 of 47

No one reads 100 pages

6 of 47

The Test Pyramid is not a Strategy.

​

Watch: Pyramids Are Ancient - Let's Talk Automation Strategy

7 of 47

Test Types

Scope & Objectives

Tools

Team Roles

Environments

Review Process

Deliverables

Exploratory Test Process

Successful Strategy is more than a Checklist

Risks

Defect Reporting

Metrics

Pass / Fail Conditions

Budget

8 of 47

Be a Test Strategy Template Consumer Architect

9 of 47

Warm Up Questions

10 of 47

The Best Type of Test Strategy?

11 of 47

One that is read.

12 of 47

The Best Test Strategy Template?

13 of 47

Does not exist.

14 of 47

Why Does it Not Exist?

15 of 47

Because projects are unique.

16 of 47

Teams Read When You

Understand your Context

Understand your Reader

Architect your own Strategy

17 of 47

Best Practice + Context

= Relevance

18 of 47

Understanding Strategy

19 of 47

What is a (Test) Strategy?

Diagnosis

Explain the challenge

Guiding Policy

The approach for addressing the challenge

Actions

Steps needed to complete the challenge

(Test) Strategy

Surmounting a key challenge

20 of 47

5 W’s and 1 How (and answering just How)

Who

What

When

Where

Why

How

How

​

How is testing technically done? (Tools, frameworks)

How is testing reported on?

21 of 47

Trying Again: Answering Who

Who

​

Whose team(s) does this strategy cover?

Who is testing? (hint: all of you)

How

​

How is testing technically done? (Tools, frameworks)

How is testing reported on?

What

When

Where

Why

22 of 47

Trying Again: Answering What

Who

​

Who’s team(s) does this strategy cover?

Who is testing? (hint: all of you)

What

​

What project?�What testing requirements?

How

​

How is testing technically done? (Tools, frameworks)

How is testing reported on?

When

Where

Why

23 of 47

Trying Again: Answering When

Who

​

Who’s team(s) does this strategy cover?

Who is testing? (hint: all of you)

What

​

What project?�What testing requirements?

When

​

When is testing required?

How

​

How is testing technically done? (Tools, frameworks)

How is testing reported on?

Where

Why

24 of 47

Trying Again: Answering Where

Who

​

Who’s team(s) does this strategy cover?

Who is testing? (hint: all of you)

What

​

What project?�What testing requirements?

When

​

When is testing required?

Where

​

Where will tests execute? Locally, static test env, dynamic test env?

How

​

How is testing technically done? (Tools, frameworks)

How is testing reported on?

Why

25 of 47

Trying Again: Answering Why

Who

​

Who’s team(s) does this strategy cover?

Who is testing? (hint: all of you)

What

​

What project?�What testing requirements?

When

​

When is testing required?

Where

​

Where will tests execute? Locally, static test env, dynamic test env?

Why

​

Why are certain test types more important than others?

(Risk...)

How

​

How is testing technically done? (Tools, frameworks)

How is testing reported on?

26 of 47

Understand your Context

27 of 47

Project Risk

Project Detail

Regulation

Context

28 of 47

Project Risks

Identify

What are the actual risks on your project?

Focus

Tailor your strategy to focus on these risks.

Mitigate

Establish actions to mitigate the risk.

29 of 47

Project Detail

Business

Value

What is the business case for this project?

​

How can that impact testing budget?

​

Requirement

How

What features are critical to the business case?

How can we test those features?

Technical

Implementation

Which technologies are we using?

How will that technology impact testing?

30 of 47

Regulation

None

Internal

External

Formality, Required Evidence & Sign Off

Architectural Freedom

31 of 47

Understand your Reader

32 of 47

Types of Reader

T

Your team

Regulators

Related Teams

Internal Stakeholders

Detail

Formality

33 of 47

Architect your own Strategy

34 of 47

Strategy Tone

Formality

  • Formal Language
  • Organisation Preferred Format
  • Organisation Defined Detail Level
  • Casual Language
  • Teams Preferred Format
  • Team Defined Detail Level
  • Formal Language
  • Externally Mandated Format (Regulator/ISO)
  • Externally Defined Level

35 of 47

Strategy Information Styles

Behavioural

Trust

Describe team behaviours and foundations of decision making.

​

Implementation

Clarity

Define how testing is done and technology used. Remove ambiguity.

Metrics

Proof

Track testing efforts over time. Make it easy to prove success.

36 of 47

Behavioural Style

Set boundaries. Trust others to make good decisions.

​

But should you always trust?

Advantages

  • Creative Freedom
  • Provides a Basis for Decision Making

Disadvantages

  • Is the team mature enough?
  • Less Implementation Guidance

Example Use Case

  • Mature Teams
  • Strong Test Culture

37 of 47

Implementation Style

Clarity at the cost of creativity?

Advantages

  • Easy to Follow the How

Disadvantages

  • Restricts Creativity
  • Only Helps with Known Challenges

Example Use Case

  • Less Mature Teams
  • Developing Test Culture

38 of 47

Metrics Style

Beware Surrogation!

Advantages

  • Track Progress Easily
  • Common Goals Across Teams

Disadvantages

  • Restricts Creativity
  • Surrogation (chasing metrics) Risk

Example Use Case

  • All Team Maturity Levels
  • Data Driven Organisations

39 of 47

You can Pick n’ Mix Information Styles!

40 of 47

Presentation Styles

Single Document

Team Focus

Everything in one easily shareable document.

​

Multiple Documents

Organisation Focus

Collection of documents - each tailored to the different type of reader.

Templates

Standardisation

Make it easy to share ideas, concepts and progress.

41 of 47

You can Pick n’ Mix Presentation Styles!

42 of 47

Lessons Learnt

43 of 47

How to Stop Teams Reading

With six easy tactics!

  • Architected in Isolation
  • Using unnecessarily complex language
  • Assumed same first language
  • Tangents
  • Waffle
  • Ego

44 of 47

How to Make Teams Read Again

And keep them involved.

  • Involve others sensibly
  • Be Concise
  • Stay Relevant
  • Avoid Copy & Paste
  • Adapt to feedback
  • Adapt to changing context

45 of 47

Wrapping Up

46 of 47

A good test strategy is like a good diet.

​

Balanced.

47 of 47

Questions?�

@tomdrivendev

https://tomdriven.dev