Computer Knowledge
Software Testing and Quality Control
2,292 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
-
We can never be certain that the program is bug free
-
We have no definite stopping point for testing, which makes it easier for somemanagers to argue for very little testing.
-
We have no easy answer for what testing tasks should always be required,because every task takes time that could be spent on other high importance tasks.
-
All of the above.
D
Correct answer
Explanation
The impossibility of complete testing has three critical consequences: we can never guarantee bug-free code (A), testing lacks a definitive stopping point allowing managers to under-test (B), and every testing task competes with other priorities for time (C). Since all three statements are valid consequences of exhaustive testing being impossible, 'All of the above' is correct.
-
Assess development plan and status
-
Develop the test plan
-
Test software design
-
Test software requirement
C
Correct answer
Explanation
The 11-step software testing process follows a logical sequence from planning through execution. 'Test software design' (C) is not the correct sequential step name - the process typically includes testing requirements, not testing design as a distinct step in this sequence. This makes C the option that breaks the proper sequence naming convention.
-
Security failures were the result of untested parts of code
-
The development team achieved complete statement and branch coverage butmissed a serious bug in the MASPAR operating system
-
An error in the code was so obscure that you had to test the function with almostevery input value to find its two special-case failures.
-
All of the above.
C
Correct answer
Explanation
In the MASPAR case study (frequently cited in software testing curricula), the main conclusion is that an error in the code was extremely obscure, requiring testing of nearly all input values to detect two specific edge-case failures. This demonstrates the limitation of standard coverage metrics, as structural coverage alone cannot guarantee the absence of such data-specific bugs.
-
True
-
False
-
Don't Know
-
May be
A
Correct answer
Explanation
In software testing and quality assurance, any deviation from the documented requirement specification is considered a defect. This is a fundamental principle - requirements define what the system should do, and any failure to meet those specifications is a defect, regardless of whether the system functions correctly in other ways. This aligns with standard QA definitions and best practices.
-
Error Guessing
-
Equivalence Class Partition
-
Boundary Value Analysis
-
None of the Above
-
True
-
False
-
Don't Know
-
May be
A
Correct answer
Explanation
In software testing and quality assurance, a defect is defined as any deviation from the specified requirements. If the actual behavior differs from what's documented in the requirement specification, it's classified as a defect - no matter how small. This is the foundational definition used in formal testing methodologies.
-
The account information to use when executing the request (Username, password)
-
The account information to use when creating the request (Username, password)
-
The account information to use when deleting the request (Username, password)
-
The account information to use when testing the request (Username, password)
A
Correct answer
Explanation
In TMF, a Test Account provides the credentials (username and password) used when executing test requests. This allows tests to run against systems requiring authentication. The key word is executing - not creating, deleting, or separately testing the request.
-
System scanning
-
Vulnerability assessment
-
System testing
-
Pentest
D
Correct answer
Explanation
Penetration testing involves actively exploiting vulnerabilities to identify security weaknesses in hardware, software, or configurations. Unlike vulnerability assessment (option B), which identifies potential issues, pentesting demonstrates their impact through exploitation. Options A and C are generic terms that don't specifically involve exploiting vulnerabilities.
B
Correct answer
Explanation
The correct testing order is Unit → Module → Integration → System → User Acceptance. Integration testing must occur BEFORE System level testing because you need integrated modules before you can test the complete system. The given order places Integration after System, which is incorrect.
-
Unit Testing
-
Monkey Testing
-
Installation Testing
-
Useability Testing
C
Correct answer
Explanation
Installation Testing specifically involves verifying that the software installs correctly according to installation documentation and manuals, and that all installation steps, prerequisites, and configuration requirements are properly documented and followed.
-
Build Acceptance Test(BAT)
-
Verification testing,
-
Sanity testing testing,
-
validation testing
D
Correct answer
Explanation
BAT, Verification, and Sanity testing are related types of preliminary testing performed to ensure basic functionality. Validation testing is the odd one out because it's a broader concept checking if the software meets user needs and requirements, not just a preliminary smoke test.
-
Volume testing is a way to test functionality.
-
Stress testing is a way to test reliability.
-
GUI Testing; Data Base Testing; Syntax Checking ; Structure Investigation ; is the type of dynamic Testing.
-
unit, integration, regression, are the Type of white box testing.
C
Correct answer
Explanation
The question asks which statement is WRONG. Option C is incorrect because GUI and database testing are dynamic, but syntax checking and structure investigation are static analysis techniques, not dynamic testing. Volume testing tests performance with large data volumes (not primarily functionality), and regression testing is not exclusively a white-box technique.
-
IT is a method by which individual units of source code are tested to determine if they are fit for use.
-
It is the testing of integrated system to evaluate the system's compliance with its specified requirements.
-
Testing that seeks to uncover software errors by partially retesting a modified program.
-
None
C
Correct answer
Explanation
Regression testing is testing performed after code modifications to verify that existing functionality remains unaffected. It selectively retests parts of the system that could be impacted by the changes. Option C correctly describes it as testing that uncovers errors by partially retesting a modified program.
-
IT is a method by which individual units of source code are tested to determine if they are fit for use.
-
It is the testing of integrated system to evaluate the system's compliance with its specified requirements.
-
Testing that seeks to uncover software errors by partially retesting a modified program.
-
None
C
Correct answer
Explanation
This is a duplicate of question 152336. Regression testing is testing performed after code modifications to verify that existing functionality remains unaffected. It selectively retests parts of the system that could be impacted by the changes.
-
Test Data
-
Checkpoints
-
Screenshots of the application under test(AUT)
-
Object Repository
C
Correct answer
Explanation
QTP's Active Screen technology captures screenshots of the application under test (AUT) as they appeared during recording. These screenshots help users insert checkpoints and parameterize objects directly from the captured UI.