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. i, iii. and iv. are more for developers.

  2. ii. and iv. are more for developers.

  3. ii, iii. and iv. are more for developers.

  4. ii. and iii. are more for developers.

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

Coverage measurement tools help developers identify which code paths haven't been executed. Dynamic analysis tools detect runtime issues like memory leaks. Performance testing typically requires QA specialists, test comparators serve testers, and incident management is used across the team.

Multiple choice technology testing
  1. Unreachable code.

  2. Unreachable Variables

  3. Faults in the requirements

  4. Too few comments

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

Static code analysis examines source code structure to identify issues like unreachable code, unused variables, and insufficient comments. It cannot detect faults in requirements because requirements are not code - they are separate documents that static analysis tools don't process.

Multiple choice technology testing
  1. Boundary Testing

  2. Ad Hoc Testing

  3. Functional Testing

  4. Mutation Testing

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

Ad Hoc testing is unstructured, exploratory testing where testers randomly try various functionality to find unexpected defects. Boundary testing checks edge values, Functional testing validates requirements, and Mutation testing modifies code to verify test suite quality. 'Breaking the system randomly' is the hallmark of Ad Hoc.

Multiple choice technology testing
  1. Ad Hoc Testing

  2. Compatibility Testing

  3. Endurance Testing

  4. Functional Testing

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

Endurance testing (also called soak testing) evaluates system stability over prolonged periods to detect issues like memory leaks, resource exhaustion, or slow degradation that only appear after extended runtime. Ad Hoc is random exploration, Compatibility checks cross-platform behavior, and Functional testing validates features.

Multiple choice technology testing
  1. Component Testing

  2. Scalability Testing

  3. Ad Hoc Testing

  4. Agile Testing

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

Agile Testing is a practice in agile development where testing is integrated throughout the development lifecycle, with development treating testing as its customer and emphasizing test-first design through techniques like TDD. It promotes continuous testing alongside development rather than as a separate phase.

Multiple choice technology testing
  1. Agile Testing

  2. Functional Testing

  3. Acceptance Testing

  4. Smoke Testing

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

Acceptance testing is performed by customers or users to verify if the software meets business requirements and is ready for deployment. Agile testing is a development methodology, functional testing focuses on feature correctness, and smoke testing verifies basic build stability rather than final acceptance.

Multiple choice technology testing
  1. Component Testing

  2. Exhaustive Testing

  3. End-to-End Testing

  4. Functional Testing

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

Exhaustive Testing aims to test every possible combination of inputs and preconditions. While theoretically complete, it's usually impractical for real-world systems due to the exponential growth of test cases with each input variable.

Multiple choice technology testing
  1. Component Testing

  2. Functional Testing

  3. Regression Testing

  4. Smoke Testing

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

Smoke testing is a preliminary testing cycle designed to ensure that the basic and most critical capabilities of a software application function correctly before proceeding to deeper test suites. Distractors like regression, functional, or component testing refer to more structured, targeted, or comprehensive testing methods.

Multiple choice technology testing
  1. Soak testing

  2. Smoke testing

  3. Agile Testing

  4. Functional Testing

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

Soak testing involves running a system under high load for an extended period to identify issues like memory leaks, performance degradation, or resource exhaustion that only appear over time. It helps ensure system stability during prolonged operation.

Multiple choice technology testing
  1. Component Testing

  2. Stress Testing

  3. Dynamic Testing

  4. Recovery Testing

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

Stress Testing pushes a system beyond its specified limits to determine breaking points and observe failure modes. It helps identify the maximum load capacity and how the system degrades or fails under extreme conditions, unlike normal load testing which stays within specifications.

Multiple choice technology testing
  1. Black Box Testing

  2. Acceptance Testing

  3. User Acceptance testing

  4. Boundary Testing

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

User Acceptance Testing (UAT) is the final testing phase where actual users validate the software against real-world requirements before purchase or deployment. While Acceptance Testing is a broader category that may include internal QA, UAT specifically involves end users performing formal evaluation as a condition of purchase.

Multiple choice technology testing
  1. Scalability Testing

  2. Benchmark Testing

  3. Mutation Testing

  4. Black Box Testing

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

Benchmark testing uses standardized, representative workloads to measure and compare system performance across different hardware or software configurations. It establishes baseline performance metrics by running typical programs and data sets through the system being evaluated.

Multiple choice technology testing
  1. Mutation Testing

  2. Component Testing

  3. Agile Testing

  4. Ad Hoc Testing

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

Mutation testing intentionally injects small code changes (mutations) to create faulty versions of the application, then runs existing tests against them. If tests fail to catch the injected bugs, it indicates the test suite needs improvement. Mutation testing evaluates test suite quality rather than application correctness.

Multiple choice technology testing
  1. Boundary Testing

  2. Smoke Testing

  3. Scalability Testing

  4. Functional Testing

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

Scalability testing measures system performance under increasing workload to determine when or if the system degrades. Unlike basic performance testing, scalability testing specifically focuses on graceful handling of growth and helps identify capacity limits before production failure.

Multiple choice technology testing
  1. test items

  2. test deliverables

  3. test tasks

  4. test environment

  5. test specification

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

IEEE 829 standard for software test documentation includes sections for test items, test deliverables, test tasks, and test environment. Test specification is not one of the standard document names - the actual documents are Test Design Specification, Test Case Specification, and Test Procedure Specification as separate entities.