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
-
TCS Program Manager
-
Functional Track Lead
-
Functional Consultant
-
Technical Consultant
C
Correct answer
Explanation
During the developer's Self Unit Testing phase, the developer (Technical Consultant) consults the Functional Consultant to clarify requirements and verify that the built logic matches the functional specifications. The TCS Program Manager and Functional Track Lead occupy higher oversight roles and are not typically consulted for unit-level testing details.
-
Exercise system functions in proportion to the frequency they will be used in the released product
-
Push the system beyond its designed operation limits and are likely to make the system fail
-
Exercise unusual and obscure scenarios that may not have been considered in design
-
Exercise the most complicated and the most error-prone portions of the system
-
i, iii, iv, v.
-
ii, iv and v.
-
i, ii and iv.
-
i and v.
-
Step Into and Step Out of a subprocess can be used
-
The process definition can be changed while debugging
-
The current process instance can be paused during testing
-
Input data can be supplied via an xml file to the process starter
A,C,D
Correct answer
Explanation
The TIBCO Designer Tester Utility allows developers to step into and out of subprocesses, pause current process instances during execution, and feed test data to process starters via XML files. However, process definitions cannot be modified dynamically during an active debugging session.
B
Correct answer
Explanation
Testing can only prove the presence of defects, not their absence. Due to the infinite path combinations and complexity of software, it is impossible to guarantee that all defects have been removed from a program, making the statement false.
-
Observability
-
Simplicity
-
Stability
-
All of the above
D
Correct answer
Explanation
Testable software exhibits observability (you can see its internal state), simplicity (easier to understand and test), and stability (consistent behavior). All three are recognized characteristics of software that is easy to test effectively.
-
Black-box testing
-
Glass-box testing
-
Grey-box testing
-
White-box testing
A
Correct answer
Explanation
Black-box testing focuses on validating functional requirements, ensuring that each program function is fully operational and produces the expected outputs for given inputs. Glass-box and white-box testing focus on internal program logic and code paths rather than verifying operational requirements from a functional perspective.
-
Behavioral testing
-
Black-box testing
-
Grey-box testing
-
White-box testing
D
Correct answer
Explanation
White-box testing (also called glass-box or structural testing) examines the internal structure and implementation details of software. It requires knowledge of the code to design test cases that cover internal paths and logic. This contrasts with black-box testing which only considers inputs and outputs.
-
Incorrect or missing functions
-
Interface errors
-
Performance errors
-
All of the above
-
None of the above
D
Correct answer
Explanation
Black-box testing validates software functionality by examining inputs and outputs without accessing internal code. It checks for incorrect or missing functions, interface errors, and performance issues by testing against specifications. This approach evaluates the system from an external user perspective, simulating real-world usage scenarios.
-
Behavioral errors
-
Logic errors
-
Performance errors
-
Typographical errors
-
Both b and d
E
Correct answer
Explanation
White-box testing examines internal program structures. Logic errors (like incorrect paths) and typographical errors (like variable misspellings that still compile but cause wrong execution flows) can be missed by black-box testing, which only verifies external inputs/outputs. Both behavioral and performance errors are typically checked in black-box testing.
-
Rely on basis path testing
-
Exercise the logical conditions in a program module
-
Select test paths based on the locations and uses of variables
-
Focus on testing the validity of loop constructs
B
Correct answer
Explanation
Condition testing is a white-box technique that focuses on exercising logical conditions within program modules. It tests various combinations of condition outcomes to ensure all logical paths are validated. The approach specifically targets decision points and boolean expressions, distinguishing it from other control structure testing techniques.
-
Rely on basis path testing
-
Exercise the logical conditions in a program module
-
Select test paths based on the locations and uses of variables
-
Focus on testing the validity of loop constructs
C
Correct answer
Explanation
Data flow testing selects test paths based on how variables are defined (assigned) and used (referenced) throughout the program. It tracks the flow of data between variable definitions and their uses to ensure coverage of data relationships. Option A describes basis path testing, option B describes condition testing, and option D describes loop testing, which are different white-box testing techniques.
-
Rely basis path testing
-
Exercise the logical conditions in a program module
-
Select test paths based on the locations and uses of variables
-
Focus on testing the validity of loop constructs
D
Correct answer
Explanation
Loop testing specifically focuses on testing loop constructs to ensure they function correctly for different scenarios. It tests loop boundaries (zero iterations, one iteration, maximum iterations, n+1 iterations) and loop termination conditions. Options A, B, and C describe different testing techniques: basis path testing, condition testing, and data flow testing respectively, which have different focuses than loop constructs.
-
Stress Testing
-
Regression Testing
-
Integration Testing
-
None
C
Correct answer
Explanation
Spring is primarily used in integration testing to test how different components work together. It allows you to load the application context, wire beans together, and test interactions between components in a near-production environment. Stress testing focuses on system limits, and regression testing checks for bugs in existing functionality.
-
Alpha Testing
-
Beta Testing
-
White Box Testing
-
Black Box Testing
A
Correct answer
Explanation
Alpha Testing occurs at the developer's site by internal staff or independent testers before release. Beta Testing happens at the customer's site with actual users in their environment. The question specifies 'at the developers' site,' which is the defining characteristic of Alpha Testing.