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 programming languages

Testing check-ins before building can be achieved through

  1. Incremental Check-ins

  2. Test driven development

  3. Gated Check-ins

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

Gated check-ins is the TFS feature that allows testing check-ins before building completes. When a developer submits a gated check-in, the build system shelves the changes, builds the project, runs tests, and only commits the changes if everything passes. This prevents broken builds from entering the repository.

Multiple choice technology platforms and products

What capability helps developers to do historical debugging?

  1. Breakpoint

  2. Intellitrace

  3. Debugger

  4. VS Debugger
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Intellitrace (formerly Historical Debugger) is the VS 2010 feature that enables historical debugging. It records events and method calls during execution, allowing developers to step backward and forward through code execution history to diagnose bugs that are difficult to reproduce.

Multiple choice technology testing

Select Security Testing tools

  1. TamperIE

  2. CookieMonitor

  3. SQL Profiler

  4. All the above
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

TamperIE modifies requests to test input validation. CookieMonitor examines cookie data for security issues. SQL Profiler helps analyze SQL injection vulnerabilities. All three are legitimate security testing tools.

Multiple choice technology testing

Security testing includes

  1. Penetration testing

  2. Vulnerability Testing

  3. Risk Assessment

  4. All the above

  5. None of the above
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Penetration testing actively exploits vulnerabilities. Vulnerability testing identifies security weaknesses. Risk assessment evaluates potential impact and likelihood. Security testing encompasses all these activities.

Multiple choice technology testing

Select security Testing Objectives

  1. Confidentiality

  2. Integrity

  3. Availability

  4. Functionality Testing

  5. All the above
Reveal answer Fill a bubble to check yourself
A,B,C Correct answer
Explanation

Confidentiality ensures data is only accessible to authorized parties. Integrity guarantees data is not altered without authorization. Availability ensures systems and data are accessible when needed. These are the three pillars of the CIA triad.

Multiple choice technology testing

Which is not a Component testing

  1. Check the memory leaks

  2. Check the robustness

  3. Check the branch coverage

  4. Check the decision tables
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Component testing focuses on individual software components. Memory leak checking, robustness testing, and branch coverage are all component-level testing activities. Decision table testing is a system-level or acceptance testing technique that examines complex business logic and decision rules, not component behavior.

Multiple choice technology testing

Contract and regulation testing is a part of

  1. System testing

  2. Acceptance testing

  3. Integration testing

  4. Smoke testing
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Contract and regulation testing verifies that software meets contractual obligations and regulatory requirements. This is a key part of acceptance testing, which validates that the system meets business and legal requirements before it's accepted by stakeholders. It's not system testing (functional verification), integration testing (interface verification), or smoke testing (basic stability check).

Multiple choice technology testing

___________ technique can be used to achieve input and output coverage

  1. Boundary value analysis

  2. Equivalence partitioning

  3. Decision table testing

  4. State transition testing
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Equivalence partitioning divides input and output domains into classes where tests from one class represent all others, achieving coverage. Boundary value analysis focuses on edge values, decision tables handle complex logic, and state transition tests model state changes.

Multiple choice technology testing

Purpose of test design technique is

  1. Identifying test conditions only, not Identifying test cases

  2. Not Identifying test conditions, Identifying test cases only

  3. Identifying test conditions and Identifying test cases

  4. Identifying test conditions or Identifying test cases
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Test design techniques serve the dual purpose of identifying test conditions (what to test) AND identifying specific test cases (how to test). Options A and B are incomplete - focusing on only one aspect. Option D incorrectly suggests 'or' instead of 'and'.

Multiple choice technology testing

Non-functional system testing includes:

  1. Testing to see where the system does not function properly

  2. Testing quality attributes of the system including performance and usability

  3. Testing a system feature using only the software required for that action

  4. Testing a system feature using only the software required for that function
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Non-functional testing examines quality attributes rather than functional behavior. This includes performance testing (speed, response time), usability testing (user experience), reliability, security, and other '-ilities'. Option A describes functional testing, while options C and D describe functional feature testing.

Multiple choice technology testing

Consider the following statements about early test design: i. early test design can prevent fault multiplication ii. faults found during early test design are more expensive to fix iii. early test design can find faults iv. early test design can cause changes to the requirements v. early test design takes more effort

  1. i, iii & iv are true, ii & v are false

  2. iii is true, i, ii, iv & v are false

  3. iii & iv are true, i, ii & v are false

  4. i, iii, iv & v are true, ii is false
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

Early test design prevents fault multiplication (catching requirements issues before implementation), finds faults early when cheaper to fix, and can cause requirement changes based on test insights. Statement ii is false - early faults are LESS expensive to fix. Statement v is situational - early design can reduce total effort despite upfront investment.

Multiple choice technology testing

Testing should be stopped when:

  1. All the planned tests have been run

  2. Time has run out

  3. All faults have been fixed correctly

  4. It depends on the risks for the system being tested
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Testing completion is risk-based, not based on arbitrary criteria like running all tests, time expiration, or fixing all faults. The decision depends on the acceptable level of residual risk for the system being tested. Options A, B, and C are incomplete approaches that don't consider business risk.

Multiple choice technology testing

Which is not a testing principle

  1. Early testing

  2. Defect clustering

  3. Pesticide paradox

  4. Exhaustive testing
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

Exhaustive testing (testing all possible inputs and combinations) is impractical and impossible for non-trivial systems - it's NOT a testing principle. Early testing, defect clustering (Pareto principle), and pesticide paradox (repeated tests become less effective) ARE recognized testing principles.