CTFL 5.5.1: Prepare a defect report

• a
  Steps: use the valid account and select Sign in. Expected: remain on login. Actual: dashboard opens; POST /session returns 200.This reverses expected and actual behavior and reports a 200 response not present in the evidence.
• ✓
  Correct answer: Steps: use the valid account and select Sign in. Expected: dashboard opens. Actual: 'Session expired'; POST /session returns 401.It records the supplied steps, expected and actual results, and relevant log response.
• c
  Steps: use the valid account and select Sign in. Expected: dashboard opens. Actual: server error; POST /session returns 500.This invents a server error and 500 response instead of the observed message and 401 response.
• d
  Steps: use the valid account and select Sign in. Expected: 'Session expired'. Actual: dashboard opens; POST /session returns 200.This treats the failure message as expected and replaces the observed 401 response with 200.

A dynamic-testing defect report typically describes the failure so it can be reproduced and resolved, including the steps, relevant logs, expected result, and actual result. Only the second description accurately transfers every supplied observation: valid account, Sign in, expected dashboard, actual 'Session expired', and HTTP 401.

Syllabus section 5.5

• ✓
  Correct answer: Transfer form: an amount entered with a decimal comma is saved without itA short, specific summary of the anomaly that was observed.
• b
  Transfer form is completely unusable and has to be fixed before the releaseThis generalizes to the whole form and states urgency rather than the anomaly.
• c
  Amount handling problem found during yesterday afternoon's test sessionThis records when the anomaly was found rather than what was observed.
• d
  Probable rounding defect in the payment component, see the attached screenshotThis speculates about the cause, which analysis rather than the report establishes.

A defect report includes a title with a short summary of the anomaly being reported. The best title states what was observed, briefly and specifically enough for the reader to identify the anomaly. A title that generalizes the severity, that describes when the anomaly was found, or that speculates about the cause does not summarize the anomaly itself.

Syllabus section 5.5

• a
  Orders 4.2.0, staging, TC-118, steps; expected: full price charged; actual: 10% deductedThe actual result misstates the observed 20% discount as 10%. The report must reflect the recorded failure.
• b
  Orders 4.2.0, production, TC-118, steps; expected: full price charged; actual: 20% deductedThe environment is wrong: the run was on staging, so this misidentifies the test environment.
• c
  Orders 4.2.0, staging, TC-118, steps; expected: full price charged; actual: the expiry check is missingThe actual result must be the observed behaviour that enables reproduction, not the tester's diagnosis of the cause.
• ✓
  Correct answer: Orders 4.2.0, staging, TC-118, steps; expected: full price charged; actual: 20% deductedTest object, environment, test case, steps and both results all match the recorded evidence.

A defect report logged during dynamic testing typically includes a title summarizing the anomaly, identification of the test object and test environment, the context of the defect such as the test case being run, a description of the failure enabling reproduction including the test steps, and the expected and actual results. Each candidate must therefore be checked both against the fields a defect report has to carry and against what was actually recorded: one candidate misstates the observed discount, one names an environment the run was not performed on, and one replaces the observed actual result with a diagnosis of its cause.

Syllabus section 5.5.1