ASTQB practice question 11 of 15

What is the primary use of teststorming?

Full set: 76 questions
Answer options
A: Load and stress testing from multiple locations
B: Testing the device’s ability to deal with weather conditions
C: Deriving test cases and test scenarios Correct answer
D: creating masses of test data
Correct Answer:
C. Deriving test cases and test scenarios
Explanation

Teststorming is a collaborative, experience-based test technique analogous to brainstorming. The primary purpose is for a diverse group of team members (e.g., testers, developers, product owners) to collectively generate test ideas, identify potential risks, and define test scenarios or charters for exploratory testing. It leverages the varied perspectives of the participants to achieve broader and deeper test coverage than an individual might devise alone. The focus is on the creative and systematic derivation of what and how to test, which is then formalized into test cases and scenarios.

Why Incorrect

A. This describes distributed load testing, a specific type of non-functional performance testing, not a collaborative test design method.
B. This is a literal, misleading interpretation of the word "storm" and refers to environmental or hardware testing, which is unrelated.
D. While test data needs may be identified during teststorming, the primary goal is creating test scenarios and cases, not the mass generation of data itself.

References

1. ISTQB® Certified Tester Advanced Level - Test Analyst (CTAL-TA) Syllabus 2019: Section 4.2, "Exploratory Testing," discusses the creation of test charters, which are a common output of collaborative test idea generation sessions like teststorming. The syllabus states, "Test charters may be created based on... brainstorming with other team members." (p. 37). This directly links the brainstorming concept to the derivation of test scenarios.

2. ISTQB® Certified Tester Foundation Level - Agile Tester (CTFL-AT) Syllabus 2014: Section 3.2.2, "The Role of a Tester in an Agile Team," emphasizes that testing activities are a shared responsibility. It states, "Testers become test coaches... sharing their knowledge and experience with others... This helps the team to get a better understanding of testing, which results in better test cases..." This collaborative derivation of test cases is the core of teststorming.

3. Itkonen, J., Mäntylä, M. V., & Lassenius, C. (2013). "The role of the tester in agile software development." 2013 ACM / IEEE International Symposium on Empirical Software Engineering and Measurement. This peer-reviewed publication describes testers in agile teams facilitating "test case/idea generation" with developers and other stakeholders, which is a formal description of the teststorming process. (Section IV.B, "Test Case/Idea Generation"). DOI: 10.1109/ESEM.2013.23.

Scroll to Top