Computer Knowledge
Software Testing and Quality Control
2,598 Questions
Software testing and quality control questions cover testing methodologies, unit testing, and defect management. These concepts are crucial for the computer knowledge sections of competitive exams. Practice these questions to understand verification and validation processes thoroughly.
Quality control typesUnit testing purposeSoftware vulnerability testingTest planning tasksLoop testing criteriaTest harness functions
Software Testing and Quality Control Questions
-
Total numbers of features to be tested
-
Testing approaches to be tested
-
Testing tools to be used
-
All of the above
D
Correct answer
Explanation
A Test Plan is a comprehensive document that details the scope, objective, target market, resources, test environments, features to be tested, test methodologies, tools, and schedule for a testing project, making all options correct.
-
Load Testing
-
Stress Testing
-
Functional Testing
-
Regression Testing
A
Correct answer
Explanation
Load testing evaluates system performance under expected load conditions. Testing the printer with exactly 100 pages in 30 seconds matches the requirement specification, making this load testing - verifying the system meets its stated performance criteria under normal load. Stress testing would exceed this limit to find breaking points.
-
Equivalence Partitioning
-
Boundary Value Analysis
-
Error Guessing
-
State Transition Testing
C
Correct answer
Explanation
Error guessing is a black box testing technique where testers use their experience and intuition to make educated guesses about where defects might exist. Unlike formal methods such as equivalence partitioning or boundary value analysis, error guessing relies on the tester's judgment to identify potential error conditions based on common mistakes.
-
Curiosity
-
A critical eye
-
Good Communication
-
All of the above
D
Correct answer
Explanation
Effective software testing requires curiosity to explore the system thoroughly, a critical eye to identify potential issues and edge cases, and good communication skills to document and report findings clearly. 'All of the above' correctly identifies that successful testing demands all these qualities combined.
-
Any tester
-
Any tester who wants to do it
-
Any tester who has understanding of software coding
-
Test Lead
C
Correct answer
Explanation
Automation testing requires programming knowledge to write and maintain test scripts. Any tester with coding understanding can perform automation testing, distinguishing it from manual testing which doesn't require coding skills. Test leads may or may not do automation - it's a technical skill, not a role-specific one.
-
System Testing
-
Unit Testing
-
Integration Testing
-
Regression Testing
D
Correct answer
Explanation
Regression testing involves re-running previously executed tests to verify that recent code changes have not adversely affected existing functionality. Re-applying tests from old builds to new builds is the classic definition of regression testing - ensuring nothing that worked before has broken.
-
What to test
-
Inputs to test
-
Expected results
-
Test Conditions and Constraints
-
All of the above
E
Correct answer
Explanation
A test case is a comprehensive specification that includes what to test, the inputs to be used, expected results, and the conditions and constraints under which testing occurs. 'All of the above' correctly identifies that test cases encompass all these elements to provide complete guidance for test execution.
-
Installation testing
-
Integration testing
-
Configuration testing
-
Regression testing
-
Stress testing
E
Correct answer
Explanation
Stress testing evaluates system behavior under extreme load conditions, often beyond expected capacity. Flooding the system with transactions to test peak performance is stress testing - it pushes the system to its limits to identify breaking points and ensure it handles overload conditions gracefully.
-
Functional testing
-
Requirements Testing
-
Regression Testing
-
User Testing
A
Correct answer
Explanation
Functional testing evaluates software based on functional requirements - what the system should do from a user perspective. It verifies that each feature of the software operates as specified in the requirements document, making 'Functional testing' the correct answer.
-
Equivalence Partitioning
-
Boundary Value Analysis
-
Error Guessing
-
State Transition Testing
B
Correct answer
Explanation
Boundary Value Analysis is a black box testing technique that focuses on testing values at the boundaries (edges) of input ranges, such as minimum and maximum values. Many defects occur at boundaries, making them critical test points. Equivalence partitioning divides inputs into classes, error guessing uses intuition, and state transition testing analyzes system states.
-
Manual Testing
-
Automation Testing
-
Functional Testing
-
Performance testing
A
Correct answer
Explanation
Ad-hoc testing is informal, unstructured testing without formal test documentation or plans. It is inherently manual as it relies on tester intuition, exploration, and creativity to find defects. While automation can support testing, ad-hoc testing by definition is an exploratory manual approach.
-
Test Matrix
-
Checklist
-
Test Bed
-
Traceablity Matrix
D
Correct answer
Explanation
A Requirements Traceability Matrix (RTM) maps each requirement to one or more test cases, creating a bidirectional trace that ensures every requirement is tested and allowing verification that no requirement has been missed.
-
Regression Testing
-
Re Testing
-
Ad-Hoc testing
-
Sanity Testing
B
Correct answer
Explanation
The question describes executing the same test case with different input values, which is commonly used to verify functionality across various scenarios. Re-testing refers to running tests again after fixes, while regression testing checks that changes haven't broken existing functionality.
-
Usability Testing
-
Security Testing
-
Black Box Testing
-
All of the above
A
Correct answer
Explanation
Usability testing evaluates how easy and intuitive a user interface is for end users. It's a non-functional testing type that assesses user experience, learnability, and efficiency rather than specific functional requirements.
-
Glass box testing
-
Closed box testing
-
Open box testing
-
Clear box testing
B
Correct answer
Explanation
White box testing requires knowledge of internal code structure. Glass box, open box, and clear box all refer to seeing inside the code. 'Closed box' refers to black box testing where internal implementation is hidden.