โ† All CTC Flashcard Decks

Anomaly Reporting Flashcards

7 cards from real CTC practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Anomaly Reporting flashcards as text
  1. A cosmetic defect that does not affect functionality but violates the UI style guide should be assigned which severity level?

    Answer: Low or minor severity

    Cosmetic issues with no functional impact are classified as low or minor severity defects.

  2. Which practice best prevents duplicate anomaly reports from being filed?

    Answer: Searching the defect tracking system before submitting a new report

    Checking existing reports before filing prevents duplicates and keeps the defect database accurate.

  3. When a defect is discovered in a third-party component integrated into the system under test, the anomaly report should:

    Answer: Be filed against the system under test and note the third-party component as the likely source

    The anomaly is still filed against the system where it was observed, with the third-party component identified as a contributing factor.

  4. What is the purpose of a defect aging report in anomaly management?

    Answer: To identify defects that have remained open beyond an acceptable time threshold

    A defect aging report highlights stale open anomalies so management can take corrective action to prevent them from blocking releases.

  5. A tester files an anomaly but the development team marks it 'Not a Defect.' The tester disagrees. What is the correct escalation path?

    Answer: Bring the dispute to the test manager or project manager for resolution with stakeholder input

    Disputed anomaly dispositions should be escalated to management for formal resolution involving relevant stakeholders.

  6. Which of the following anomaly report fields ensures traceability back to the test plan?

    Answer: Test case or test procedure identifier

    Referencing the test case or procedure ID links the anomaly to the specific planned test that uncovered it, maintaining traceability.

  7. The 'defect leakage' metric in anomaly management measures:

    Answer: Defects that escaped testing and were found in production by end users

    Defect leakage quantifies the testing team's missed detections by counting defects that reached production unfound.

How this page was made: written with AI tools. We have not yet matched this exam's facts to an official source, so confirm fees, dates and rules with the exam body. Not reviewed by a subject-matter expert. Editorial policy