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. only important in system testing

  2. only used in component testing

  3. most useful when specified in advance

  4. derived from the code

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

Expected results are most valuable when predicted before test execution to avoid confirmation bias. They are critical at all testing levels (not just component or system testing) and must be derived from requirements or design, not from the code.

Multiple choice technology testing
  1. report on deviations from the project plan

  2. sign the system off for release

  3. re-allocate resource to meet original plans

  4. raise incidents on faults that they have found

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

Test managers should report deviations from project plans, should raise incidents on faults they find, and should NOT unilaterally sign off releases (that's a business decision). However, re-allocating resources just to meet original plans is poor practice - plans should adapt to current realities. Resources should be re-allocated based on current priorities and risks, not to force adherence to outdated plans. Flexibility is more important than rigid plan adherence.

Multiple choice technology testing
  1. how to fix the fault

  2. how to reproduce the fault

  3. test environment details

  4. severity, priority

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

A test incident report documents what was found, not how to fix it. It must include reproduction steps (B), test environment details (C) for context, and severity/priority (D) to triage. The actual fix is a development task, determined after root cause analysis - this is not part of the incident report itself.

Multiple choice technology testing
  1. performance, load and stress testing

  2. requirements-based testing

  3. usability testing

  4. top-down integration testing

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

System testing tests the complete integrated system. Performance/load/stress (A), requirements-based (B), and usability (C) all test the system as a whole. Top-down integration testing (D) is an integration strategy - it's about how modules are combined during development, not a system-level test of the complete product.

Multiple choice technology testing
  1. expected outcomes are defined by the software’s behaviour

  2. expected outcomes are derived from a specification, not from the code

  3. expected outcomes include outputs to a screen and changes to files and

  4. expected outcomes should be predicted before a test is run

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

Expected outcomes must be derived from specifications or requirements, not from the software's actual behavior itself. If derived from the software, bugs would be accepted as correct behavior. All other options describe true traits of expected outcomes.

Multiple choice technology testing
  1. ISO/IEC 12207

  2. BS7925-1

  3. BS7925-2

  4. ANSI/IEEE 829

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

BS 7925-1 is the standard specifically dedicated to the vocabulary and definitions of software testing terms. BS 7925-2 defines testing techniques, ISO/IEC 12207 is for lifecycle processes, and ANSI/IEEE 829 defines test documentation templates.

Multiple choice technology testing
  1. What is not to be tested

  2. Test environments

  3. Quality plans

  4. Schedules and deadlines

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

Under the IEEE 829 Standard for Software Test Documentation, a test plan includes scope, environments, and schedules. A quality plan is a distinct document detailing broader organizational quality assurance processes and metrics.

Multiple choice technology testing
  1. No, because they are normally applied before testing

  2. No, because they do not apply to the test documentation

  3. Yes, because both help detect faults and improve quality

  4. Yes, because testing includes all non-constructive activities

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

Reviews and inspections ARE considered part of testing in the broad sense - they detect defects and improve quality before dynamic testing begins. Option A is wrong because being 'before testing' doesn't exclude them from being testing activities. Option B is incorrect - reviews do apply to test documentation. Option D overgeneralizes. Option C correctly states both help detect faults and improve quality.

Multiple choice technology testing
  1. Measuring response time

  2. Measuring transaction rates

  3. Recovery testing

  4. Simulating many users

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

Performance testing measures how the system performs under load - response time (A), transaction rates (B), and simulating many users (D) are all core performance testing activities. Recovery testing (C) verifies the system can recover from crashes/failures and restore data - this is about reliability and availability, not performance speed or throughput.

Multiple choice technology testing
  1. After more formal techniques have been applied

  2. By inexperienced testers

  3. After the system has gone live

  4. Only by end users

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

Error guessing leverages the tester's experience to find edge cases, making it most effective after formal, systematic techniques are applied. It requires testing experience and is done during testing stages rather than post-live or by end users only.

Multiple choice technology testing
  1. Deviation from expected result to actual result

  2. Defect in the software.

  3. Error in the program code.

  4. Fault in the system.

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

Failure is the dynamic, observable deviation of the software from its expected behavior or specifications. Defects, errors, and faults are static flaws in the code or human mistakes that can lead to failures during execution.

Multiple choice technology testing
  1. Analysts

  2. Management

  3. Developers

  4. Testers

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

Technical reviews require active participation from technical staff who examine the work product. This includes analysts who review requirements, developers who review code, and testers who review test cases. Management typically does not participate directly in technical reviews - they may receive summary outcomes but are not participants examining the technical details.

Multiple choice technology testing
  1. Regression testing.

  2. Integration testing.

  3. Error Guessing.

  4. System testing.

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

Error guessing is an informal, experience-based technique used to supplement systematic, rigorous testing methodologies. Regression, integration, and system testing are formal levels or types of testing that are part of the main test process.

Multiple choice technology testing
  1. Performance testing

  2. Recovery testing

  3. GUI testing

  4. User requirements.

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

To solve this question, the user needs to understand the purpose of capture and replay facilities in software testing and the types of testing methods that can utilize them.

Capture and replay facilities are typically used to record interactions with a software application and then replay them at a later time. This can be useful for automating certain types of testing, as it allows testers to quickly and easily repeat a set of actions without having to manually perform them each time.

Now, let's go through each option and explain why it is right or wrong:

A. Performance testing: This option is incorrect. Capture and replay facilities can be very useful for performance testing, as they allow testers to simulate large numbers of user interactions and monitor how the application responds. This can help identify performance bottlenecks and other issues.

B. Recovery testing: This option is incorrect. Capture and replay facilities can also be useful for recovery testing, as they allow testers to simulate various error conditions and test how the application responds to them.

C. GUI testing: This option is incorrect. Capture and replay facilities can be very useful for GUI testing, as they allow testers to automate repetitive tasks such as clicking buttons or filling out forms.

D. User requirements: This option is correct. While capture and replay facilities can be used to test user requirements, they are not typically the best choice for this type of testing. User requirements testing typically involves validating that the software meets specific user needs or business requirements, which may require more complex testing methods.

Therefore, the correct answer is:

The Answer is: D. User requirements.