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
In the V-Model of software development, acceptance testing corresponds to which development phase?
Answer: Requirements analysis
In the V-Model, acceptance testing validates against the requirements defined in the requirements analysis phase.
Which defect severity level typically indicates that the system crashes or critical functionality is completely unusable?
Answer: Critical/Blocker
A Critical or Blocker severity means the defect causes system failure or prevents all testing/use of core functionality.
What is the key difference between alpha testing and beta testing?
Answer: Alpha is done internally; beta is done by actual end users in their environment
Alpha testing occurs at the developer's site with internal staff, while beta testing is done by real users in their own environment.
A CSM is implementing Continuous Integration (CI). How does CI primarily support quality assurance?
Answer: By automatically building and testing code with each commit to catch defects early
CI integrates code frequently and runs automated tests on each commit, enabling early detection of integration defects.
Which technique involves intentionally introducing defects into software to evaluate the effectiveness of the test suite?
Answer: Fault injection / Mutation testing
Mutation testing (fault injection) introduces small code mutations to check whether the existing tests can detect the introduced defects.
Which standard provides guidelines specifically for software test documentation such as test plans and test reports?
Answer: IEEE 829
IEEE 829 is the standard for Software and System Test Documentation, covering test plans, designs, cases, and summary reports.
A team practicing Test-Driven Development (TDD) writes tests before code. What is the PRIMARY quality benefit of TDD?
Answer: It ensures code is written to satisfy well-defined, testable requirements from the start
TDD drives design from testable requirements, resulting in code that inherently meets its specifications and is easier to maintain.