Question 1: What is the main purpose of test case design techniques?
- Reduce coding effort
- Increase test coverage efficiently
- Automate testing
- Eliminate bugs completely
Explanation: Test design techniques help maximize coverage with fewer test cases.
This intermediate Software Testing quiz focuses on practical testing concepts, real-world scenarios, test design techniques, defect management, and process-oriented QA knowledge. Ideal for testers with basic experience preparing for interviews and professional testing roles.
Explanation: Test design techniques help maximize coverage with fewer test cases.
Explanation: Equivalence Partitioning groups similar input values.
Explanation: Boundary Value Analysis targets edge cases.
Explanation: Decision tables map combinations of business rules.
Explanation: A test condition is an aspect of the system to be tested.
Explanation: The test plan defines testing scope and approach.
Explanation: Regression testing ensures changes do not break existing features.
Explanation: Smoke testing validates build stability.
Explanation: False positives are incorrectly reported defects.
Explanation: Exploratory testing relies on tester experience.
Explanation: Automation improves speed and repeatability.
Explanation: Non-functional testing validates performance, security, etc.
Explanation: Defect leakage occurs when bugs reach production.
Explanation: Recovery testing verifies system recovery.
Explanation: Load testing evaluates performance under normal load.
Explanation: RTM ensures all requirements are tested.
Explanation: Deferred defects are postponed.
Explanation: Integration testing checks data flow between modules.
Explanation: Compatibility testing checks multiple environments.
Explanation: Scenarios describe high-level functionality.
Explanation: State transition testing validates state changes.
Explanation: Entry criteria define when testing can begin.
Explanation: Exit criteria define when testing can stop.
Explanation: UI testing checks layout and consistency.
Explanation: High severity defects affect core functionality.
Explanation: Acceptance testing validates business requirements.
Explanation: Volume testing checks large data handling.
Explanation: Re-testing verifies defect fixes.
Explanation: Endurance testing checks long-term stability.
Explanation: Database testing validates data integrity.
Explanation: Usability testing focuses on user experience.
Explanation: Defect triage prioritizes and reviews defects.
Explanation: API testing validates backend services.
Explanation: Security testing identifies vulnerabilities.
Explanation: Unit testing is usually done by developers.
Explanation: Test coverage measures how much is tested.
Explanation: Compatibility testing checks backward compatibility.
Explanation: Acceptance testing validates workflows.
Explanation: Metrics track testing effectiveness.
Explanation: Recovery testing validates crash recovery.
Explanation: Migration testing verifies data accuracy.
Explanation: Installation testing verifies setup and removal.
Explanation: Compliance testing ensures legal adherence.
Explanation: Concurrency testing checks simultaneous access issues.
Explanation: Spike testing checks sudden load changes.
Explanation: Acceptance testing confirms release readiness.
Explanation: Configuration testing validates settings.
Explanation: Regression testing ensures stability after changes.
This intermediate Software Testing quiz focuses on practical testing concepts, real-world scenarios, test design techniques, defect management, and process-oriented QA knowledge. Ideal for testers with basic experience preparing for interviews and professional testing roles.