โ† All CSM Flashcard Decks

Quality Assurance & Testing Practices Flashcards

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

Read the first 7 Quality Assurance & Testing Practices flashcards as text
  1. Which testing level verifies that separately developed software modules work correctly when combined?

    Answer: Integration testing

    Integration testing focuses on the interactions and interfaces between modules or components after unit testing.

  2. A CSM is reviewing a process where developers examine each other's code for defects. This is best described as:

    Answer: Peer code review

    Peer code review is a static testing technique where developers inspect each other's code to find defects before execution.

  3. Which metric measures the percentage of source code lines executed during testing?

    Answer: Statement coverage

    Statement coverage measures the percentage of executable statements that have been exercised by the test suite.

  4. User Acceptance Testing (UAT) is BEST described as testing performed by:

    Answer: End users or clients to validate the system meets business needs

    UAT is conducted by end users or clients to ensure the system satisfies real-world business requirements before go-live.

  5. In risk-based testing, test priority is determined by:

    Answer: The likelihood and impact of potential failures

    Risk-based testing prioritizes test effort based on the probability that a feature will fail and the severity of that failure.

  6. Which document formally records the details of a test case including inputs, expected results, and execution steps?

    Answer: Test script

    A test script (or test case document) specifies the exact steps, inputs, and expected outcomes for executing a test.

  7. What is the main goal of regression testing after a software defect is fixed?

    Answer: To ensure the fix did not introduce new defects in existing functionality

    Regression testing confirms that a bug fix or change has not broken previously working functionality.