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

Multiple choice technology testing
  1. Checking test logs against the exit criteria specified in test planning.

  2. Logging the outcome of test execution.

  3. Assessing if more tests are needed.

  4. Writing a test summary report for stakeholders

Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Exit criteria evaluation involves checking logs, assessing if more tests are needed, and writing reports. Logging the outcomes of test execution is part of the Test Execution phase, not a task of evaluating or executing the Exit criteria phase itself.

Multiple choice technology testing
  1. Load Testing

  2. Integration Testing

  3. System Testing

  4. Usability Testing

Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Load testing involves subjecting a system to varying workloads to measure performance characteristics like response time, throughput, and resource utilization. It helps identify performance bottlenecks and ensures the system functions properly under different load conditions. Integration testing focuses on interfaces between components, system testing validates the complete system, and usability testing evaluates user experience - none specifically test workload performance behavior.

Multiple choice technology testing
  1. System Level Testing

  2. Integration Level Testing

  3. Unit Level Testing

  4. Component Testing

Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Integration level testing specifically targets the interfaces and interactions between integrated components or modules. It exposes defects that occur when components work together, such as data flow problems, interface mismatches, or timing issues. System level testing evaluates the complete system, unit testing focuses on individual components, and component testing isolates specific parts - none specifically target inter-component interfaces.

Multiple choice technology testing
  1. The analysis of batch programs.

  2. The reviewing of test plans.

  3. The analysis of program code

  4. The use of black box testing

Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Static analysis involves examining program code without executing it to find defects, vulnerabilities, or violations of coding standards. It uses automated tools or manual review to analyze source code structure, logic, and potential errors. Batch programs and test plans are not analyzed, and black box testing is dynamic (requires execution) rather than static.

Multiple choice technology testing
  1. Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

  2. Concurrently designing & testing the application.

  3. Single user testing, determining the effects of accessing the same application.

  4. Mainly concurrency testing refers to testing the application once it is fully designed.

Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Concurrency testing is multi-user testing that evaluates what happens when multiple users or processes access the same application code, module, or database records simultaneously. It identifies locking issues, deadlocking problems, and single-threaded code that should be multi-threaded. Option A correctly describes this testing approach. Options B, C, and D incorrectly describe concurrent design, single-user testing, or post-design testing - none of these capture the essence of concurrency testing.

Multiple choice technology testing
  1. Status reports are the elaborated results of testing cycle. These reports contain success of the product.

  2. Status reports are the brief results of end to end testing cycle. These reports contain success of the product.

  3. Status reports are the elaborated results of testing cycle. These reports contain success, warning and alerts of the product, just to ensure that there are no bugs in the product.

  4. Status reports are the brief results of end to end testing cycle. These reports contain success, warning and alerts of the product, just to ensure that there are no show stoppers or blockers or hiccups in the product.

Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Status reports provide concise summaries of end-to-end testing cycles, highlighting success metrics, warnings, and critical alerts. They help stakeholders quickly assess product quality and identify any showstoppers, blockers, or significant issues. Option D correctly captures this - brief results focusing on critical issues. Options A and B incorrectly omit warnings/alerts, while option C incorrectly states reports are elaborated and claim to ensure no bugs (impossible).

Multiple choice technology testing
  1. Testing each end of the application.

  2. Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

  3. Testing each module of the application and make sure each of them is working fine.

  4. Testing each module of the application and making sure that none of them is having any bug.

Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

End-to-end testing validates a complete application flow in an environment that mimics real-world use, including interactions with databases, networks, hardware, and other external systems. Option B accurately describes this holistic approach. Options A and C are incomplete (testing only ends or modules), while option D focuses on bug-free modules rather than complete integrated workflows.

Multiple choice technology testing
  1. If there is a discrepancy in code then the best approach is to check the use case documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the project manager.

  2. If there is a discrepancy in code then the best approach is to check the use case documents for bugs. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the project manager.

  3. If there is a discrepancy in code then the best approach is to check the requirement documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the business analyst

  4. If there is a discrepancy in code then the best approach is to check the requirement documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the QA lead.

Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

When there's a disagreement about expected functionality, the requirements documents are the authoritative source. If uncertainty remains after checking requirements, the business analyst is the right person to consult as they own the requirement definition. Options A and B incorrectly mention use case documents instead of requirements, and option D involves the QA lead who doesn't own requirements.

Multiple choice technology testing
  1. Running a system for a long period of time. For example,running the application for 2-3 days.If the application doesnt work properly then it is sent back to the devlopment team .

  2. Soak testing refers to the testing of individual module of the application & making it error free.

  3. Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of t

  4. .Running a system at low load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of t

Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Soak testing involves running a system under high load (or typical production load) for a continuous, prolonged period to detect performance degradation, memory leaks, or resource exhaustion. The other options describe running at low load or general non-loaded execution without testing performance under prolonged strain.

Multiple choice technology testing
  1. Testing the pre-recorded messages in the Interactive voice response systems.

  2. Testing the messages in the Interactive voice response systems.

  3. Testing the internel working of the Interactive voice response systems.

  4. Testing the call routing/path of the Interactive voice response systems.

Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

IVR (Interactive Voice Response) testing validates pre-recorded audio messages, prompts, and voice menus within automated phone systems. Option A correctly identifies testing pre-recorded messages as the core activity. Option B is vague about what message aspects to test. Option C incorrectly suggests testing internal workings rather than user-facing audio. Option D incorrectly focuses on call routing rather than message testing.

Multiple choice technology testing
  1. Static test

  2. Dynamic test

  3. Smoke test

  4. None of these

Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

A smoke test is specifically performed on a new or candidate build to verify that its crucial functions work and that the build is stable enough to proceed with further, more detailed testing. Static and dynamic tests are broader categories, not the specific initial build verification test.

Multiple choice technology testing
  1. TIN

  2. TAC

  3. DEV

  4. All of these

Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Agent testing in Q&I is always performed in the TAC (Testing Agent Console) environment. This is a dedicated environment for agent-based testing, distinct from DEV (development) and TIN regions which serve other purposes.

Multiple choice technology mainframe
  1. TAR rules verification

  2. Scorecard Attributes

  3. Tier Cutoffs

  4. All the above

Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

The three basic levels in scorecard testing are TAR rules verification, Scorecard Attributes, and Tier Cutoffs. TAR (Transparent Account Rating) rules verify the scoring logic is applied correctly, scorecard attributes define the variables used in scoring, and tier cutoffs establish the boundaries between risk segments. 'All the above' is correct because it encompasses all three levels.

Multiple choice technology testing
  1. I, II & III

  2. II, III & IV

  3. I, II & IV

  4. I, III & IV

Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

The correct answer is C. I, II & IV.

Explanation: I. It strives to ensure that quality is built into software: This statement is true as software verification and validation programs aim to ensure that quality is built into the software development process. II. It provides management with insights into the state of a software project: This statement is true as a software verification and validation program provides management with insights into the progress, quality, and state of a software project. III. It ensures that alpha, beta, and system tests are performed: This statement is not necessarily true for all software verification and validation programs. While these types of tests are commonly performed, it is not a requirement for all programs. IV. It is executed in parallel with software development activities: This statement is true as a software verification and validation program typically runs concurrently with software development activities to ensure that quality is maintained throughout the development process.

Therefore, the correct answer is C. I, II & IV.