nerdexam
BCS-ISEB

ISEB-SWTINT1 · Question #49

Scenario 2 Your organisation is a large media services corporation (MSC). MSC uses Agile development, within a Scrum framework. Here, the iterations are referred to as Sprints. For each Sprint, a…

The correct answer is B. Creating test cases as part of test design. Option B is correct because user-stories, by design, are intentionally brief (1-2 lines) and describe what the customer wants without specifying how or to what measurable standard - this ambiguity hits hardest at test design, where testers must derive specific, verifiable test…

The Testing Process

Question

Scenario 2 Your organisation is a large media services corporation (MSC). MSC uses Agile development, within a Scrum framework. Here, the iterations are referred to as Sprints. For each Sprint, a set of user-stories is defined, built, and tested. The user-stories are typically 1-2 lines long, indicating what the customer wants the system to do. MSC is in the process of updating its website to meet the recently introduced accessibility rules for websites. Accessibility means the availability of a system suitable to members of the public with, for example, visual or hearing difficulties. It has been decided to start with two requirements, as its first 2 Sprints: 1) Presentation of content with clear headings, short sentences, text versions always available. 2) Consistent navigation through the website. You are the test manager and there are four developers and two testers. You have all worked together previously, and are very experienced in MSCs products. Although the accessibility rules are new to you and the team, you have all attended a workshop where they were explained. Which stage of the Fundamental Test Process will be most affected by the use of user-stories as defined above?

Options

  • ACreating a schedule of activities as part of test planning.
  • BCreating test cases as part of test design.
  • CCreating the test environment as part of test execution.
  • DAssessing requirements coverage at the end of each Sprint.

How the community answered

(45 responses)
  • A
    7% (3)
  • B
    80% (36)
  • C
    11% (5)
  • D
    2% (1)

Explanation

Option B is correct because user-stories, by design, are intentionally brief (1-2 lines) and describe what the customer wants without specifying how or to what measurable standard - this ambiguity hits hardest at test design, where testers must derive specific, verifiable test cases. For example, "clear headings" and "consistent navigation" give no concrete acceptance criteria, so a tester cannot determine the exact conditions, inputs, or expected results needed to write a valid test case.

Why the distractors are wrong:

  • A (test planning/scheduling): Sprint schedules are driven by team capacity and sprint length, not by how user-stories are worded - the planning process remains largely unaffected.
  • C (test environment setup): The environment needed for accessibility testing (browsers, screen readers, etc.) depends on the type of testing, not the format of the requirements.
  • D (requirements coverage assessment): While vague stories do make coverage harder to measure, this is a downstream symptom - the root problem is that you couldn't write adequate test cases in the first place during design.

Memory tip: Think of user-stories as a restaurant menu item with no ingredients list. You know the dish you want (the goal), but you can't write a recipe (test cases) without knowing the specifics - that gap is always felt in the kitchen (test design), not when booking a table (planning) or checking the bill (coverage assessment).

Topics

#test design#Agile testing#user stories#Scrum

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full ISEB-SWTINT1 Practice