Skip to content
← All CTFL glossary terms

Defect report

Documentation of a failure or anomaly, including the information needed to reproduce, analyze, and resolve it.

Syllabus chapters: 5

Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.

Related terms

Defect report in a practice question

Question 1

A tester prepares a defect report from this evidence. Build: web shop 4.2.0, staging. Test data: active account user17 with a valid password. Step 1: open the login page and enter the test data. Step 2: select Sign in. Expected: the account dashboard opens. Actual: the page shows 'Session expired' and stays on login. Log: POST /session returns 401. Which description should the tester enter so the report accurately supports reproduction and resolution?

  1. Steps: use the valid account and select Sign in. Expected: remain on login. Actual: dashboard opens; POST /session returns 200.
  2. Steps: use the valid account and select Sign in. Expected: dashboard opens. Actual: 'Session expired'; POST /session returns 401.
  3. Steps: use the valid account and select Sign in. Expected: dashboard opens. Actual: server error; POST /session returns 500.
  4. Steps: use the valid account and select Sign in. Expected: 'Session expired'. Actual: dashboard opens; POST /session returns 200.
Show answer
  • 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.
  • 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.
  • 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

Question 2

Three weeks after a release the team has to reproduce exactly the test results obtained for that release. How does configuration management make this possible?

  1. It re-runs the test suite against the current baseline of the test environment
  2. It keeps the earlier baseline, so the team can revert to it and reproduce the results
  3. It re-derives the test cases from the requirements that were in force back then
  4. It restores the defect reports raised at the time so the results can be read again
Show answer
  • It re-runs the test suite against the current baseline of the test environmentThe current baseline is not the one that produced those results, so re-running it proves nothing.
  • Correct answer: It keeps the earlier baseline, so the team can revert to it and reproduce the resultsReverting to the previous baseline is how previous test results are reproduced.
  • It re-derives the test cases from the requirements that were in force back thenConfiguration management tracks existing work products rather than deriving test cases anew.
  • It restores the defect reports raised at the time so the results can be read againDefect reports record what was found; they do not reproduce the test results themselves.

In testing, configuration management identifies, controls and tracks work products such as test plans, test cases, test scripts, test results and test logs as configuration items. Once a configuration item is approved for testing it becomes a baseline and can only be changed through a formal change control process; configuration management keeps a record of changed configuration items when a new baseline is created, and it is possible to revert to a previous baseline to reproduce previous test results.

Syllabus section 5.4.1

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.