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. Quality Assurance

  2. Quality Control

  3. Defect management

  4. Software testing

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

Defect detection and correction is Quality Control - it involves inspecting the product to find and fix defects. Quality Assurance focuses on preventing defects through process improvement. Defect management is the tracking system, and Software testing is the broader activity. The detection-correction cycle is reactive QC, not preventive QA.

Multiple choice technology testing
  1. V model

  2. Agile model

  3. X model

  4. Waterfall model

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

V model, Agile model, and Waterfall model are well-known software development/testing models. The 'X model' is not a recognized testing or development model in standard software engineering literature. This appears to be a fabricated option to test fundamental knowledge of testing models.

Multiple choice technology testing
  1. Low

  2. Medium

  3. High

  4. Should not be prioritized

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

Severity 1 indicates the most critical defects (system crash, data loss, complete feature failure). Such high-severity defects must receive high or urgent priority for resolution. Assigning 'Low' priority to a Severity 1 defect would be inappropriate because the impact is critical, even if frequency is low. Priority must align with severity for critical issues.

Multiple choice technology testing
  1. Scenario generator

  2. Defect Management tool

  3. Regression testing tool

  4. Test data generator

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

Bugzilla is a widely-used web-based bug tracking and defect management system developed by Mozilla. It's used for reporting, tracking, and managing defects/issues. It's not for scenario generation, regression testing automation, or test data generation - its primary and well-known purpose is defect/issue management.

Multiple choice technology testing
  1. Semantic Errors

  2. Syntax Errors

  3. Common Errors

  4. Logic Errors

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

The Information Pane in QTP/UFT displays Syntax Errors that occur during test creation and execution. Semantic Errors, Common Errors, and Logic Errors are not the standard error types shown in this pane. Syntax errors relate to code structure and grammar violations.

Multiple choice technology testing
  1. A. A Do Loop

  2. B. Recovery Scenario

  3. C. IFHEN statement

  4. D. Selectase statement

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

To handle unpredictable testing exceptions, one can use recovery scenarios.

Option A, Do Loop, is a programming construct used to execute a block of code repeatedly. It is not relevant to handling unpredictable testing exceptions.

Option B, Recovery Scenario, is a feature of automation testing tools that allows you to define a set of actions to be taken when a particular exception or error occurs during test execution. This option is the correct answer.

Option C, IFTHEN statement, is a conditional statement used in programming to execute a block of code based on a particular condition. It is not directly relevant to handling unpredictable testing exceptions.

Option D, Selectase statement, is not a valid programming construct or feature of automation testing tools.

Therefore, the correct answer is:

The Answer is: B. Recovery Scenario.

Multiple choice technology web technology
  1. Component testing should be performed by development

  2. Component testing is also know as isolation or module testing

  3. Component testing should have completion criteria planned

  4. Component testing does not involve regression testing

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

Component testing absolutely does involve regression testing to ensure code changes don't break existing functionality within the component. The statement 'Component testing does not involve regression testing' is false, making option D the correct answer to this negative question.

Multiple choice technology web technology
  1. Variables not defined in the code

  2. Spelling and grammar faults in the documents

  3. Requirements that have been omitted from the design documents

  4. How much of the code has been covered

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

To solve this question, the user needs to understand what inspections are and what they are used for. Inspections are a type of static testing that involves a team of individuals examining code, documents, or other deliverables to identify defects or areas for improvement.

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

A. Variables not defined in the code: This option is correct. Inspections can help identify variables that have not been defined in the code, which can cause errors or unexpected behavior when the code is executed.

B. Spelling and grammar faults in the documents: This option is correct. Inspections can also help identify spelling and grammar errors in documents, which can affect the readability and clarity of the document.

C. Requirements that have been omitted from the design documents: This option is correct. Inspections can also help identify requirements that have been omitted from the design documents, which can lead to incomplete or incorrect designs.

D. How much of the code has been covered: This option is incorrect. Inspections are not typically used to determine code coverage. Code coverage is typically measured using tools such as test coverage analyzers or profiling tools.

Therefore, the answer is: D. How much of the code has been covered.

Multiple choice technology testing
  1. Identifies the bottlenecks in an application

  2. Performance testing covers functional testing fully

  3. Performance Tuning

  4. Establish baseline for future testing

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

Performance testing focuses on system responsiveness, stability, and speed under load - NOT functional correctness. It identifies bottlenecks, aids performance tuning, and establishes baselines, but does not verify functional behavior which is the domain of functional testing.

Multiple choice technology testing
  1. Soak Testing

  2. Smoke Testing

  3. Adhoc testing

  4. Mutation Testing

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

Soak testing (also called endurance testing) is a performance testing type that checks system stability under extended load. Smoke testing is quick basic testing, adhoc is informal testing, and mutation testing involves modifying code to check test suite quality - none are performance testing types.

Multiple choice technology testing
  1. Silk Test

  2. Jmeter

  3. Rational Robot

  4. Bugzilla

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

JMeter is a dedicated performance testing tool designed for load and stress testing. Options A, C (Silk Test, Rational Robot) are functional testing tools, and D (Bugzilla) is a bug tracking system - none are performance testing tools.

Multiple choice technology testing
  1. Test Plan

  2. Design

  3. Analyze

  4. Final Testing and Implementation

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

Performance Testing is conducted during the final stages of STLC, specifically in the 'Final Testing and Implementation' phase. Before performance testing, the application must be functionally stable. Performance testing requires a near-production environment and comes after functional, integration, and system testing are complete.