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
-
a) Structural Testing
-
b) Design Based Testing
-
c) Error Guessing Technique
-
d) Experience Based Technique
A
Correct answer
Explanation
White box testing evaluates the internal structure and code of software, which is why it is called structural testing. Error guessing and experience-based testing are black-box, non-structural techniques.
-
a) Security Testing
-
b) Recovery Testing
-
c) Performance Testing
-
d) Functionality Testing
A
Correct answer
Explanation
Security testing focuses on uncovering vulnerabilities in the system that could be exploited by malicious actors, including viruses and other external threats. Recovery testing verifies system restoration after failures, performance testing measures responsiveness under load, and functionality testing checks if features meet requirements without addressing security concerns.
-
a) Checking test logs against the exit criteria specified in test planning.
-
b) Logging the outcome of test execution.
-
c) Assessing if more tests are needed.
-
d) Writing a test summary report for stakeholders.
B
Correct answer
Explanation
Logging the outcome of test execution is part of the test execution phase, not exit criteria evaluation. Exit criteria tasks include assessing test logs against plans, deciding if more tests are needed, and writing summary reports.
-
a) Load Testing
-
b) Integration Testing
-
c) System Testing
-
d) Usability Testing
A
Correct answer
Explanation
Load testing evaluates how a system performs under different workload conditions, measuring response times, throughput rates, and resource utilization. The goal is to determine if the system can handle expected and peak loads while maintaining proper functionality, which directly matches the description of subjecting the target to varying workloads.
-
a) System Level Testing
-
b) Integration Level Testing
-
c) Unit Level Testing
-
d) Component Testing
B
Correct answer
Explanation
Integration testing specifically focuses on detecting defects in the interfaces and interactions between integrated components. Unit testing examines individual components, while system testing checks the entire integrated system.
-
a) The analysis of batch programs.
-
b) The reviewing of test plans.
-
c) The analysis of program code.
-
d) The use of black box testing
C
Correct answer
Explanation
Static analysis examines source code or compiled code without running the program to identify defects, security vulnerabilities, and coding standard violations. It's performed on the code itself, not on test plans or through black box execution techniques, making 'analysis of program code' the accurate description.
-
Java Profiler
-
Testing tool
-
IDE
-
None
A
Correct answer
Explanation
JProbe is a specialized Java suite used for profiling runtime performance, memory usage, threads, and code coverage. It is not an IDE (like Eclipse or IntelliJ) or a general functional testing tool, making the Java Profiler option the correct choice.
-
A. Memory Analysis, Performance Analysis, Code Coverage Analysis
-
B. Memory Analysis, Stress Test Analysis, Code Analysis
-
C. Performance Analysis, Static Analysis, Performance Analysis
-
D. None
A
Correct answer
Explanation
JProbe is a suite consisting of tools for memory debugging, performance profiling, and code coverage analysis. The distractors are incorrect because JProbe does not perform static analysis or stress testing, which are typically handled by other tools or IDE features.
-
Functional Testing
-
Unit Testing
-
Performance Testing
-
Integration Testing
B
Correct answer
Explanation
Code Coverage Analysis is used during unit testing to measure which lines/branches/paths of code are executed by test cases. It helps QA developers identify untested code, improve test completeness, and ensure critical code paths are exercised. It's not primarily for functional, performance, or integration testing (though it can complement them).
-
Method
-
Line
-
Line With Condition
-
All
D
Correct answer
Explanation
JProbe's Code Coverage Analysis provides multiple granularity levels for measuring how thoroughly your tests exercise the code. Method coverage tracks which methods were called, Line coverage tracks which lines of code were executed, and Line With Condition (also called branch coverage) tracks whether all possible outcomes in conditional statements were tested. The 'All' option means all these coverage levels are available for comprehensive testing assessment.
-
Line data, Conditional Data, Switch Data
-
Missed Column, Switch data, Conditional Data
-
Missed Column, Switch data, Unconditional Data
-
None
B
Correct answer
Explanation
In the context of the specific certification or tool pool this question belongs to, the data collected during code coverage analysis is categorized as Missed Column, Switch data, and Conditional Data. The other options contain incorrect combinations of coverage types.
-
Memory Analysis
-
Performance Analysis
-
Coverage Analysis
-
Static Analysis
A
Correct answer
Explanation
When an application continuously crashes, it often indicates memory issues such as memory leaks, null pointer exceptions, or out-of-memory errors. Memory Analysis helps identify these problems by tracking object allocations, garbage collection patterns, and memory usage patterns that lead to crashes. Performance Analysis would be used for slowness or hanging, Coverage Analysis for test completeness, and Static Analysis for code quality without running the application.
-
Automate the test
-
Add validations
-
Run this regularly as a part of build cycle
-
All of the Above
D
Correct answer
Explanation
Visual Studio Coded UI Tests support automation of UI interactions, adding validation assertions, and can be integrated into build cycles for regression testing. Since it supports all these capabilities (automation, validation, build integration), 'All of the Above' is correct. Coded UI Tests are part of Visual Studio Enterprise for automated functional testing of applications.
-
Project Server
-
Team Foundation Server
-
Integration Server
-
Exchange Server
B
Correct answer
Explanation
Coded UI Tests in Visual Studio 2010 were designed to work seamlessly with Team Foundation Server for automated testing within the application lifecycle management workflow. Project Server, Integration Server, and Exchange Server are not directly integrated with Coded UI testing capabilities.
-
Coded UI Test
-
Coded Web Test
-
Manual Test
-
Load Test
A
Correct answer
Explanation
Visual Studio 2010 introduced Coded UI Tests as a new test type, enabling automation of user interface actions through code rather than just manual or web performance tests.