QuestionQ39

Testing in Agile

You are defining the test approach for an Agile project release that will develop an improved user interface for a golf club's booking system, together with additional features that will enable more flexible bookings across the three courses. The improvements have been driven primarily by customer complaints that the booking system is difficult to follow and restrictive. The release will be split into six two-week sprints.

The stakeholders have completed a risk assessment for the release and determined that, although the system is not mission critical, customer business could be lost; therefore, a High risk level has been agreed. Because there may be a high degree of change to the screen design and functionality across the sprints, a regression-averse strategy is recommended.

Which option (1 to 4) in the table below represents the BEST test approach for this release, using these symbols?

  • ++ (highly recommended)
  • + (recommended)
  • o (neutral/optional)
  • - (not recommended)
  • -- (not to be used)

Question Image

Explanation

When an Agile release carries high risk but also undergoes substantial change to screen design and functionality across sprints, a regression-averse strategy should favor only moderate investment in test automation (since automated, especially UI-driven, checks require continual rework as the interface changes) while placing strong emphasis on exploratory testing, which can rapidly investigate new and altered functionality without first building brittle scripts, supplemented by moderate manual black-box testing for adequate risk coverage. This balance corresponds to the table row combining moderate automation, high exploratory testing, and moderate manual testing.

Community Discussion

No comments yet. Be the first to start the discussion!