Test strategy

[dialex]

Links

• https://danashby.co.uk/2017/12/13/a-new-model-for-test-strategies/ ✅
• https://testautomationu.applitools.com/setting-a-foundation-for-successful-test-automation/chapter1.html ❌
• http://www.satisfice.com/blog/archives/63 ❌
• http://www.satisfice.com/tools/tpe-model.pdf ✅
• https://mavericktester.com/2020/01/13/emergent-strategy/ ✅
• Context Driven Testing ❌
• Risk driven (series of posts) ❌
• Risk mapping https://bughuntersam.com/visual-risk-ui-automation-framework/ ✅
• http://www.brendanconnolly.net/test-driven-testing-no-testing-unless-you-have-identified-an-objective/ ❌
• https://martinfowler.com/articles/practical-test-pyramid.html ❌
• https://dojo.ministryoftesting.com/lessons/the-one-page-test-plan ✅
• https://testing.googleblog.com/2016/06/the-inquiry-method-for-test-planning.html ✅
• http://webtestingbasics.com/page/index ❌
• http://katrinatester.blogspot.pt/2015/09/continuous-delivery-testing-pathway.html ❌
• https://www.devmynd.com/blog/five-factor-testing/ ✅
• devops planning https://danashby.co.uk/2016/10/19/continuous-testing-in-devops/ ❌
• https://club.ministryoftesting.com/t/test-strategy-documentation-in-an-agile-world/10724/5 ✅
• https://club.ministryoftesting.com/t/managing-your-tests-do-you-do-that-to-what-end/11411 ❌
• https://dojo.ministryoftesting.com/lessons/how-to-write-a-software-test-plan ✅
• https://thelifeofoneman.com/the-testing-strategy ✅
• https://bughuntersam.com/a-mobile-app-test-strategy/ ✅

Ideas:

• 1 page https://making.stuff.co.nz/testing-stuff-a-one-page-test-strategy/ ❌
• ideas http://erik.brickarp.se/2016/08/how-to-come-up-with-test-ideas.html ✅
• ideas https://twitter.com/DMGreenlees/status/799380114492387328 ❌
• ideas http://erik.brickarp.se/2016/11/test-plan-questions.html ✅
• https://katrinatester.blogspot.pt/2018/05/9-quick-ideas-for-flexible-testing.html ✅
• book "Fifty Quick Ideas To Improve Your Tests" ❌

[dialex]

Test Plan Document: A test plan document is any document intended to convey test plan information. However, test plan documents are not the only source of information about the test plan. Test plan information is also contained in the oral tradition of the project and the culture of the company.

Test Strategy: The test strategy is the way tests will be designed and executed to support an effective quality assessment. Test strategy is the plan for what parts of the product will be covered by tests and what test techniques will be used. Test strategy is distinct from the logistics of implementing the strategy. Test strategy is essentially the “brains” of the test process.

[dialex]

A good test strategy is a rich collage of different processes, techniques and tools.

-- Mark Winteringham

[dialex]

Adapted from GRATEDD SCRIPTS mnemonic by Jared Quinert

Goals

• What would be true if we succeeded?
• What are the must haves?

Risks

• Do you forsee any obstacle to achieve that?
• Do you have any concerns or fears?

Approach & Tooling

• (see Ways of Working)

Schedule

• Any important dates?
• Any recurring events?

Trade-offs & Prioritisation

• Who will set priorities?
• What can we drop to prioritise our goal?

Dependencies

• Is our delivery influenced by someone/thing outside our team?

Stakeholders

• Who's the sponsor? Who has a stake in our success?
• Who reviews/approves our delivery?

Environments

• How many do we need and for what?
• Who will manage them?

Data

• What kind of data should we collect?
• How do we display that data?

Coverage & Resources & Information

• What is meaningful to test?
• What questions are our tests going to answer?
• Who is available to test?

[dialex]

See MIDTESTD mnemonic it's a subset of GRATEDD SCRIPTS