Testing Approaches

Question 1

What are the two techniques of test approach?

Proactive approach initiates [redacted]

Reactive approach starts testing after [redacted]

Answer 1

Proactive approach initiates testing early to find defects, while reactive approach starts testing after design and coding are completed.

Question 2

What are the three common approachs to implement functional testing?

Answer 2

Black, White, and Gray Box Testing

Question 3

What does functionality testing examine in a coding system?

A mnemonic is E-CA-P-S-C

Answer 3

Functionality testing examines how a system respond to expected usage, excluding cosmetic appearance, performance, security, or compliance

Question 4

Describe the purpose of functionality testing

Functionality testing verifies that [redacted],

providing a [redacted] for [redacted]

Answer 4

Functionality testing verifies that a system performs as expected, providing a stable basis for evaluating system development progress.

Question 5

What are the main types of tests in functional involved in functional testing?

Mnemonic is U-I-S-R-U

Answer 5

Unit tests, integration tests, sanity checks, regression tests, and usability acceptance tests are involved in functional testing

The following mentioned are done in order.

Question 6

What is the purpose of unit tests?

Ensure [redacted]

Answer 6

Ensure each block code products correct outputs for the next module

Question 7

What do integration tests verify?

Confirm [redacted] and [redacted[

Answer 7

Confirm proper connection and data flow between unit modules

Question 8

What is the goal of sanity checks?

Ensure [redacted]

Answer 8

Ensure code modifications don’t cause unexpected issues in unrelated parts.

Question 9

What do regression tests include?

Confirm [redacted] and [redacted]

Answer 9

Confirm new features and fixes don’t introduce new problems.

Question 10

What is usability acceptance testing?

Verification of [redacted] before [redacted]

Answer 10

Verification of system operation in its intended context before deployment

Question 11

What distinguishes Black Box Testing from White Box Testing?

Answer 11

Black Box Testing focuses on inputs and outputs without knowing the code details, while White Box Testing examines code internals to verify code robustness.

Question 12

When is White Box Testing typically performed during the development process?

It is performed during [redacted] and [redacted] of the [redacted]

Answer 12

It is performed during unit testing and early integration phases of the development process

Question 13

What characterizes Gray Box Testing?

Often performed during the crossover zone between [redacted] and [redacted]

Answer 13

Gray Box Testing is a mix of Black Box and White Box Testing, often performed during the crossover zone between integration and usability testing.

Question 14

How has Agile development influenced functional testing?

Emphasizes three factors. Mnemonic is TA-IOQ-D

(cont) to ensure [redacted] despite shorter release cycles

Answer 14

It emphasizes test automation, the integration of quality and development to ensure software quality despite shorter release cycles.

Question 15

What type of tests are best suited for automation?

Three factors. Mnemonic is R-CS-WDP.

Answer 15

Tests that require repetition, complex setups, or well-defined procedures are best suited for automation.

Question 16

Why is test documentation considered valuable?

Helps in [redacted] and [redacted]

Answer 16

It helps in maintaining quality despite time constraints and serves as a reference for test processes and defect reports.

Question 17

How does Agile development integrate quality and development?

Answer 17

By seating quality engineers alongside developers, fostering collaboration and cross-pollination of skills.

Question 18

Proactive approach initiates testing after design and coding are completed, while reactive approach starts testing early to find defects.

Answer 18

False

The statements are “flipped”.

Question 19

Black Box Testing, White Box Testing, and Gray Box Testing are commonly used for functional testing.

Answer 19

True

Question 20

Functionality testing examines how a system responds to expected usage, including cosmetic appearance, performance, security, and compliance.

Answer 20

False

Not including, but excluding.

Question 21

Functionality testing verifies that a system performs as expected when its features are used, providing an unstable basis for evaluating system development progress.

Answer 21

False

Provides a stable basis, not unstable

Question 22

Unit tests, Integration tests, Sanity checks, Regression tests, and Usability acceptance tests are involved in functional testing.

Answer 22

True

Question 23

Black Box Testing, White Box Testing, and Gray Box Testing are not commonly used approaches for functional testing.

Answer 23

False

Question 24

Black Box Testing focuses on inputs and outputs without knowing the code details, while White Box Testing does not examine code internals to verify robustness.

Answer 24

False

White Box Testing does examine code internals

Question 25

White Box Testing is performed during unit testing and early integration phases of the development process.

Answer 25

True

Question 26

Gray Box Testing is a mix of Black Box and White Box Testing, often performed during the early stages of development.

Answer 26

False

during the crossover zone between integration and usability testing.

Question 27

Agile development emphasizes test automation and the integration of quality and development to ensure software quality despite longer release cycles.

Answer 27

False

Not longer, but shorter release cycles

Question 28

Tests that require repetition, complex setups, or well-defined procedures are best suited for automation.

Answer 28

True

Question 29

Test documentation does not help in maintaining quality despite time constraints and does not serve as a reference for test processes and defect reports.

Answer 29

False

It does.

Question 30

Agile development integrates quality and development by seating quality engineers alongside developers, fostering collaboration and cross-pollination of skills.

Answer 30

True