Computer Knowledge

Software Testing and Quality Control

2,598 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
  1. Production

  2. Staging

  3. Development

  4. ABE

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

Development is the environment where code/config changes are initially implemented and tested. Staging is for pre-production validation, and Production is the live environment. Making changes directly in Production is against standard practices, making Development the correct answer.

Multiple choice technology testing
  1. SilkTest component that receives testing commands from the SilkTest Host and interacts with AUT (Application Under Test) directly.

  2. SilkTest Agent usually runs on the same machine where AUT is running.

  3. Agent cannot be classified.

  4. SilkTest component that receives testing commands from the SilkTest Host and interacts with AUT (Application Under Test) through DOM.

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

The SilkTest Agent is the component that resides on the target system (where the application under test runs) to execute commands received from the SilkTest Host. It interacts directly with the application, rather than wrapping interactions solely through a browser's DOM.

Multiple choice technology testing
  1. A list of all objects on the home page, such as HtmlImage, HtmlText, HtmlLinks, etc

  2. Testcases to execute.

  3. Commentary information

  4. An object of class BrowserChild window that holds application home page.

Reveal answer Fill a bubble to check yourself
A,C,D Correct answer
Explanation

A test frame in SilkTest stores application state information including: all objects on the home page (HtmlImage, HtmlText, HtmlLinks), commentary information for documentation, and the BrowserChild window object that holds the application home page. Test cases themselves are stored in test plan files, not in the test frame.

Multiple choice technology testing
  1. Group test

  2. Batch run

  3. Batch Test

  4. Common test

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

In QTP, running multiple tests together is called Batch Test. This feature allows you to execute a series of tests in sequence without manual intervention. Option A (Group test) and B (Batch run) are not the standard terminology used in QTP documentation.

Multiple choice technology testing
  1. Recovery scenerio

  2. Recovery types

  3. Exception handler

  4. onexit

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

QTP handles exceptions using Recovery Scenarios, which allow you to define trigger events, recovery operations, and post-recovery test run options. This is QTP's built-in mechanism for handling unexpected events, errors, or application crashes during test execution. Option C (Exception handler) is a general programming term but not QTP-specific.

Multiple choice technology testing
  1. wait

  2. waitproperty

  3. sleep

  4. getproperty

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

The waitproperty method is used for synchronization in QTP. It pauses test execution until a specified object property achieves a certain value or times out. This is the preferred synchronization method over static waits like wait() or sleep() because it waits dynamically based on application state rather than fixed time intervals.

Multiple choice technology testing
  1. Agile software development

  2. dynamic software development

  3. RAD

  4. PAD

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

Code-driven test automation is a key feature of Agile software development. Agile emphasizes continuous testing and test automation as integral parts of the development process, with code-driven tests supporting continuous integration, regression testing, and rapid feedback cycles. RAD (Rapid Application Development) and PAD are different methodologies not primarily characterized by code-driven automation.

Multiple choice technology testing
  1. code-driven testing

  2. Event - driven Testing

  3. Data-driven testing

  4. Key - driven Testing

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

Data-driven testing framework involves creating test scripts that operate on different sets of input data and expected results, stored externally. The same test script can be executed multiple times with different data combinations, maximizing test coverage with minimal script maintenance. Code-driven testing focuses on script logic, while key-driven testing uses data tables for step-by-step execution.

Multiple choice technology testing
  1. script procedures with full functionality

  2. modules, sections, and functions of the application.

  3. Scripting procedures for creating the framework.

  4. different modules from diferent applications

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

Test script modularity framework requires creating small, independent scripts representing modules, sections, and functions of the application. Each script encapsulates a specific component or functionality, promoting reusability and maintainability. These modular scripts can be combined to form larger test scenarios, reducing redundancy and making updates easier when application changes occur.

Multiple choice technology testing
  1. State tansition diagrams

  2. Finite State Machines weighted by probabilities on transitions.

  3. entity relelation ship diagram

  4. data flow diagram

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

Markov chains in Model-Based Testing are best understood as Finite State Machines weighted by probabilities on transitions. Each state represents a test condition, and transitions represent possible paths with associated probabilities. This allows statistical generation of test cases and coverage assessment based on transition likelihoods. State transition diagrams are unweighted, while entity-relationship and data flow diagrams represent different modeling concepts.