CTFL_SYLL_4.0 · Question #108
You are a functional tester, performing system testing of a flight reservation application. After logging into the system, you selected the "New Reservation" option on the main menu, and clicked the…
The correct answer is A. The test environment in which the test was executed. Option A is correct because the test environment (OS, browser, hardware, application version, network configuration, etc.) is essential information in a defect report - without it, developers cannot reproduce the issue or determine whether it's environment-specific. The report…
Question
You are a functional tester, performing system testing of a flight reservation application. After logging into the system, you selected the "New Reservation" option on the main menu, and clicked the "Submit" button without making any changes to the default values on the screen. The system charged your test credit card for $523.00 instead of the expected $1046.00. This happens every time you execute the test case. You are entering a defect into your system, and submitting it to development for correction. Your defect report currently includes:
- The date of the incident
- The identity of the tester who discovered the incident
- The steps executed to cause the incident, noting 100% reproducibility
- The impact on the system and the priority of the defect
- The expected and actual results
What information is missing from this defect report?
Options
- AThe test environment in which the test was executed
- BTest case expected results
- CThe name of the developer who should have caught their error in unit testing
- DFrequency of occurrence
How the community answered
(56 responses)- A73% (41)
- B9% (5)
- C4% (2)
- D14% (8)
Explanation
Option A is correct because the test environment (OS, browser, hardware, application version, network configuration, etc.) is essential information in a defect report - without it, developers cannot reproduce the issue or determine whether it's environment-specific. The report already includes expected/actual results (eliminating B), so B is not missing. C is wrong because defect reports are never used to assign blame to developers; they document facts, not fault. D is wrong because the report explicitly states "100% reproducibility," which fully communicates frequency of occurrence.
Memory tip: Think of a defect report as a recipe - someone else must be able to recreate the dish exactly. The "kitchen" (environment) is just as critical as the steps and ingredients.
Topics
Community Discussion
No community discussion yet for this question.