CAST Ch 8 Flashcards Preview

Certified Associate in Software Testing > CAST Ch 8 > Flashcards

Flashcards in CAST Ch 8 Deck (15):
1

Acceptance Testing

The objective of acceptance testing is to determine throughout the development cycle that all aspects of the development process meet the users needs.

2

Corrective Controls

Corrective controls assist individuals in the investigation and correction of causes of risk exposures that have been detected.

3

COTS

Commercial Off the Shelf (COTS) software products that are ready-made and available for sale in the marketplace.

4

Defect Management

Process to identify and record defect information whose primary goal is to prevent future defects.

5

Detective Controls

Detective controls alert individuals involved in a process so that they are aware of a problem.

6

Driver

Code that sets up an environment and calls a module for test. A driver causes the component under test to exercise the interfaces. As you move up the drivers are replaced with the actual components.

7

Environmental Controls

Environmental controls are the means which management uses to manage the organization.

8

Fitness for Use

Meets the needs of the customer/user.

9

Preventive Controls

Preventive controls will stop incorrect processing from occurring.

10

Selective Regression Testing

The process of testing only those sections of a program where the tester’s analysis indicates programming changes have taken place and the related components.

11

Stub

Special code segments that when invoked by a code segment under testing, simulate the behavior of designed and specified modules not yet constructed.

12

Test Cycle

Test cases are grouped into manageable (and schedulable) units called test cycles. Grouping is according to the relation of objectives to one another, timing requirements, and on the best way to expedite defect detection during the testing event. Often test cycles are linked with execution of a batch process.

13

Test Data

Data points required to test most applications; one set of test data to confirm the expected results (data along the happy path), a second set to verify the software behaves correctly for invalid input data (alternate paths or sad path), and finally data intended to force incorrect processing (e.g., crash the application).

14

Test Data Management

A defined strategy for the development, use, maintenance, and ultimately destruction of test data.

15

Test Harness

A collection of test drivers and test stubs