TM12 practice question 2 of 15

Which of the following would you expect to be most likely an example of a demotivating factor for testers? Number of correct responses: 2

Full set: 65 questions
Answer options
A: The management asks the testers to be kept informed about the intensity, quality and results of testing
B: The testers’ recommendations to improve the system or its testability are adopted by the development team
C: The same regressions tests are manually executed by the same testers, for every product release, without regression test tools Correct answer
D: The testers are assessed on whether and how often they detect important and critical failures
E: Test quality is measured by counting the number of customer/user reported problems. Correct answer
Correct Answer:
C. The same regressions tests are manually executed by the same testers, for every product release, without regression test tools; E. Test quality is measured by counting the number of customer/user reported problems.
Explanation

Demotivating factors for testers often stem from repetitive, unchallenging work and unfair performance metrics. Manually executing the same regression tests repeatedly (C) is tedious, lacks intellectual stimulation, and is inefficient, which can significantly lower morale. Using the number of customer-reported problems as a primary measure of test quality (E) is also highly demotivating. This metric unfairly places blame on the test team for defects that escape to production, ignoring factors like project constraints, inherent code quality, and the impossibility of exhaustive testing. It fosters a culture of blame rather than collaborative quality improvement.

Why Incorrect

A. Management staying informed about testing is a positive sign that the work is considered important and visible, which is typically motivating, not demotivating.
B. When a tester's recommendations are adopted, it demonstrates that their expertise is valued and their contributions have a tangible impact, which is a strong motivating factor.
D. Assessing testers on finding important failures is a core part of their role. While it can be implemented poorly, the principle itself recognizes their primary value contribution.

References

1. ISTQB® Advanced Level Syllabus, Test Manager (Version 2012), Section 5.2.3, "Individual Motivation." This syllabus, foundational for BCS certifications, explicitly lists "Repetitive work (e.g., running manual regression tests)" as a common demotivator for testers. This directly supports option C. The section also emphasizes the need for fair evaluation, contrasting with the blame-oriented metric described in option E.

2. Kaner, C., Bach, J., & Pettichord, B. (2002). Lessons Learned in Software Testing: A Context-Driven Approach. Wiley. In Chapter 2, "The Role of the Tester," the authors discuss various testing anti-patterns. Lesson 29, "Don't use bug counts as a measure of tester performance," explains how such metrics can be misleading and demotivating, creating perverse incentives. This reasoning directly supports why option E is a demotivating factor.

3. Kasurinen, J. (2017). Software Test Management. Springer International Publishing. In Chapter 4, "Test Team and People Management," Section 4.3, "Motivation," the author discusses that "monotonous and repetitive work" is a key reason for low motivation in testing teams. This provides academic support for option C being a significant demotivating factor.

Scroll to Top