CAST Ch 7 Flashcards Preview

Certified Associate in Software Testing > CAST Ch 7 > Flashcards

Flashcards in CAST Ch 7 Deck (25):
1

Actors

Interfaces in a system boundary diagram. (Use Cases)

2

Alternate Path

Additional testable conditions are derived from the exceptions and alternative course of the Use Case.

3

Boundary Value Analysis

A data selection technique in which test data is chosen from the “boundaries” of the input or output domain classes, data structures, and procedure parameters. Choices often include the actual minimum and maximum boundary values, the maximum value plus or minus one, and the minimum value plus or minus one.

4

Branch Combination Coverage

Branch Condition Combination Coverage is a very thorough structural testing technique, requiring 2n test cases to achieve 100% coverage of a condition containing n Boolean operands.

5

Branch/Decision Testing

A test method that requires that each possible branch on each decision point be executed at least once.

6

Cause-Effect Graphing

Cause-effect graphing is a technique which focuses on modeling the dependency relationships between a program’s input conditions (causes) and output conditions (effects). CEG is considered a Requirements-Based test technique and is often referred to as Dependency modeling.

7

Condition Testing

A structural test technique where each clause in every condition is forced to take on each of its possible values in combination with those of other clauses.

8

Data Flow Analysis

In data flow analysis, we are interested in tracing the behavior of program variables as they are initialized and modified while the program executes.

9

Decision Table

A tool for documenting the unique combinations of conditions and associated results in order to derive unique test cases for validation testing.

10

Equivalence Partitioning

The input domain of a system is partitioned into classes of representative values so that the number of test cases can be limited to one-per-class, which represents the minimum number of test cases that must be executed.

11

Error Guessing

Test data selection technique for picking values that seem likely to cause defects. This technique is based upon the theory that test cases and test data can be developed based on the intuition and experience of the tester.

12

Happy Path

Generally used within the discussion of Use Cases, the happy path follows a single flow uninterrupted by errors or exceptions from beginning to end.

13

Modified Condition Decision Coverage

A compromise which requires fewer test cases than Branch Condition Combination Coverage.

14

Pair-Wise

Pair-wise testing (also known as all-pairs testing) is a combinatorial method used to generate the least number of test cases necessary to test each pair of input parameters to a system.

15

Path Testing

A test method satisfying the coverage criteria that each logical path through the program be tested. Often, paths through the program are grouped into a finite set of classes and one path from each class is tested.

16

Population Analysis

Analyzes production data to identify, independent from the specifications, the types and frequency of data that the system will have to process/produce. This verifies that the specs can handle types and frequency of actual data and can be used to create validation tests.

17

Post Conditions

A list of conditions, if any, which will be true after the Use Case finished successfully.

18

Pre-Conditions

A list of conditions, if any, which must be met before the Use Case can be properly executed.

19

Sad Path

A path through the application which does not arrive at the desired result.

20

Scenario Testing

Testing based on a real-world scenario of how the system is supposed to act.

21

Statement Testing

A test method that executes each statement in a program at least once during program testing.

22

Structural Analysis

Structural analysis is a technique used by developers to define unit test cases. Structural analysis usually involves path and condition coverage.

23

System Boundary Diagram

A system boundary diagram depicts the interfaces between the software under test and the individuals, systems, and other interfaces. These interfaces or external agents are referred to as “actors.” The purpose of the system boundary diagram is to establish the scope of the system and to identify the actors (i.e., the interfaces) that need to be developed. (Use Cases)

24

Use Case

A Use Case is a technique for capturing the functional requirements of systems through the interaction between an Actor and the System.

25

User Story

A short description of something that a customer will do when they use an application (software system). The User Story is focused on the value or result a customer would receive from doing whatever it is the application does.