Software Testing Quiz & Flashcards

Regression testing checks that new changes don't adversely affect existing functionality, unlike other types that have different focuses.

Unit testing focuses on validating individual code units, unlike performance, usability, or security testing.

TDD stands for Test-Driven Development, an approach where tests are written before code, unlike other terms listed.

Beta testing is performed by end-users in their environment, unlike alpha, unit, or integration testing.

A test case includes conditions and expected results, not code, manuals, or specifications.

Static testing involves code review without execution, unlike dynamic, load, or stress testing.

Usability testing focuses on user-friendliness, unlike performance, security, or compatibility testing.

Black-box testing doesn't require code access, while white-box does, differing from other aspects listed.

Exploratory testing is useful for discovering unexpected issues, unlike automation, documentation, or load testing.

A mock object simulates a component for testing, unlike users, test cases, or defect reports.

Unit testing is performed first to validate individual components before system or acceptance testing.

A test plan outlines the testing strategy, unlike other options which involve different aspects of development.

Equivalence partitioning reduces test cases by dividing inputs into partitions, unlike improving performance or security.

Performance testing assesses speed and stability, unlike security, correctness, or code simplification.

A test summary report is created post-testing to summarize activities, unlike phases before or during development.

Smoke testing ensures basic functionality, unlike security testing, load tests, or documentation.

Defect density measures defects per size, not speed, satisfaction, or cost.

Security testing identifies vulnerabilities, unlike functionality, design, or speed improvements.

Traceability ensures test coverage by linking cases to requirements, not reducing time or simplifying design.

A test harness executes and reports tests, unlike documenting, managing projects, or designing interfaces.

Load testing assesses expected usage, while stress testing goes beyond limits, differing from speed or tool requirements.

Automated testing increases efficiency, unlike user interfaces, design, or manual testing improvements.

Acceptance testing validates software for release, unlike improving structure, design, or execution speed.

Boundary value analysis tests edges of input ranges, not interfaces, performance, or security.

Integration testing evaluates interactions between components, not user satisfaction, security, or automation.

A bug tracking system manages defects, unlike designing, executing tests, or performance improvements.

Cross-browser testing ensures consistency across browsers, not execution speed, security, or design simplicity.

System testing verifies the entire system, unlike testing components, improving code, or speed.

Risk-based testing prioritizes based on risks, not user interfaces, automation, or design enhancements.

A test summary report provides an overview of testing activities, not design improvements, performance enhancement, or code documentation.

A QA engineer designs and implements tests, unlike developing interfaces, managing projects, or writing code.

Usability testing focuses on user-friendliness, unlike performance, security, or integration testing.

Test automation aims to execute tests automatically, not improve design, interfaces, or security.

A test strategy outlines the testing approach, not software development, code quality improvement, or user experience enhancement.

Alpha testing is performed internally by developers and testers, unlike beta or acceptance testing.

A test script provides instructions for test execution, not documentation, interface design, or performance metrics.

Continuous testing in DevOps ensures rapid feedback, not design improvement, security, or interface enhancement.

Boundary value analysis focuses on testing edge cases, not design, security, or performance improvements.

Integration testing checks if new code works with existing code, unlike unit, system, or usability testing.

Configuration testing assesses performance on different setups, not interfaces, code quality, or security.

UAT verifies that user needs are met, unlike improving code efficiency, design, or performance.

Validation checks user needs, while verification checks specifications, unrelated to speed, cost, or tools.

Regression testing ensures new code doesn't break existing functionality, unlike improving interfaces, security, or design.

A test oracle predicts expected outcomes, not improving design, performance, or code documentation.

Pair testing combines expertise of two testers, not speeding execution, simplifying code, or enhancing interfaces.