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

You will use the recording mode for an object not recognized by QuickTest.

  1. Low-Level Recording Mode

  2. Normal recording Mode

  3. Analog Mode

  4. None of the above
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Low-Level Recording captures coordinates and mouse/keyboard operations at the screen level when QuickTest cannot recognize an object. Normal Recording relies on object recognition, while Analog Mode is specifically for continuous mouse movements like drawing.

Multiple choice technology testing

The method used for sending information to the test results.

  1. Reporter.log()

  2. Reporter.reportevent()

  3. Reporter.msgbox()

  4. Reporter.report()
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Reporter.ReportEvent() is the correct QTP method for sending information to the test results with a status and description. Reporter.Report() does not exist, Reporter.Log() is not a standard method, and Reporter.MsgBox() displays a message box rather than reporting to results.

Multiple choice technology testing

..... specifies the time interval(in seconds) during which quick test attempt to perform the checkpoint successfully

  1. check timeout

  2. checkpoint interval timeout

  3. checkpoint timeout

  4. quicktest timeout
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Checkpoint timeout specifies the time interval in seconds during which QuickTest attempts to perform a checkpoint operation successfully. Check timeout and checkpoint interval timeout are not standard QTP terms.

Multiple choice technology operating systems

_________ is used to determine the success or failure of a SCSI Command.

  1. Status Code

  2. Check Condition

  3. Sense Data

  4. KCQ
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

SCSI commands return a Status Code byte to indicate whether the command completed successfully or encountered an error. The Status Code is the primary mechanism for determining command outcome - GOOD indicates success, while CHECK CONDITION signals an error that requires reading Sense Data for details. Check Condition is one specific status code, not the general mechanism, and KCQ is not a standard SCSI term.

Multiple choice technology performance

Which is the central console from which Load test is managed?

  1. Analyzer

  2. VuGen

  3. Controller

  4. Generator
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

The Controller is the central console for managing and executing load tests in LoadRunner. It orchestrates load generators, manages the test execution, and monitors results. VuGen creates scripts, Analyzer analyzes results after test completion, and Generator is not a standard component.

Multiple choice technology testing

Verification is:

  1. Checking that we are building the right system

  2. Checking that we are building the system right

  3. Performed by an independent test team

  4. Making sure that it is what the user really wants
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Verification is the process of checking that we are building the system right - that is, ensuring the system is being built correctly according to specifications and requirements. Validation (option A) is checking that we're building the right system - that it meets user needs. Option C describes a specific organizational approach, not the definition. Option D describes validation, not verification.

Multiple choice technology testing

Which of the following is not a static testing technique :

  1. Error guessing

  2. Walkthrough

  3. Data flow analysis

  4. Inspections
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Static testing techniques involve examining code and documentation without running the software. Walkthroughs, data flow analysis, and inspections are all static testing techniques. Error guessing is a dynamic testing technique where testers guess likely error conditions based on experience - it requires executing the software.

Multiple choice technology testing

During which test activity could faults be found most cost effectively :

  1. Execution

  2. Design

  3. Planning

  4. Check Exit criteria completion
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Identifying and resolving faults during the planning phase is highly cost-effective because requirements and design issues can be corrected before code is written. Fixing defects in later stages like design, execution, or exit criteria review requires significantly more time, effort, and resources.

Multiple choice technology testing

The inputs for developing a test plan are taken from :

  1. Project plan

  2. Business plan

  3. Support plan

  4. None of the above
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

The test plan is primarily derived from the project plan, which contains scope, schedule, resources, and risk information needed for test planning. Business plans focus on financial/projection aspects. Support plans are for maintenance. The project plan provides the foundational information for developing an appropriate test strategy.

Multiple choice technology testing

Function/Test matrix is a type of :

  1. Interim Test report

  2. Final test report

  3. Project status report

  4. Management report
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

A Function/Test Matrix (also called a Traceability Matrix) maps test cases to requirements or functions. In many project management and testing frameworks, this matrix serves as a project status report showing coverage progress. The other options are specific report types, while the matrix is a broader status tracking tool.