High importance Flashcards Preview

Certified Associate in Software Testing > High importance > Flashcards

Flashcards in High importance Deck (41):
1

Workbench

The objective of the workbench is to produce the defined output products (deliverables) in a
defect-free manner.

2

Waterfall

Most closely resembles a “generic” model for software development

System Conceptualization
System analysis
System design
Coding
Testing
(Stop sitting so close thom)

3

Top-Down

Begin testing from the top of the module hierarchy and work down to the bottom using interim stubs to simulate lower interfacing modules or programs. Modules are added in descending hierarchical order.

(Stubs simulate the behaviors of a lower level module)

4

Bottom-Up

Begin testing from the bottom of the hierarchy and work up to the top. Modules are added in ascending hierarchical order. Requires the development of driver
modules, which provide the test input, that call the module or program being tested, and display test output.

(Drivers call the module(s) being tested)

5

Code Inspection

A formal analysis of the program source code to find defects as defined by meeting computer system design specifications.

Developers and SME's perform

6

Review

1

7

Walkthrough

An informal review (static) testing process in which the author “walks through” the deliverable with the review team looking for defects.

used to confirm understanding, test ideas, & brainnstorm.

8

White Box

A testing technique that assumes that the path of the logic in a program unit or component is known. Consists of testing paths, branch by branch, to produce predictable results.

9

Black Box

A test technique that focuses on testing the functionality of the program, component, or application against its specifications without knowledge of how the system is constructed

10

Cost of Quality

Money spent beyond expected production costs to ensure that the product the customer receives is a
quality product.

The Cost of Quality includes prevention, appraisal, and failure costs.

11

Failure Costs

All costs associated with defective products that have been moved into production.

Failure costs can be classified as either “internal” failure costs or “external” failure costs.

12

Coverage testing

A part of White-box testing

Ensures that each statement within a program is executed at least once.

13

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.

14

Branch/Decision testing

Seeks to ensure that every branch from every
decision has been executed.

15

Benefits Realization Test

A test conducted after an application is moved into production to determine whether it is likely to meet the originating business case.

16

Configuration

1

17

Conversion

Validates the effectiveness of data conversion processes, including field-to-field mapping, and data translation.

18

Exploratory testing

Aligned with the Context Driven testing school of thought.

tester learns things that, together with experience
and creativity, generates new good tests to run

quality of the testing is dependent on the tester’s skill of inventing test cases and finding defects. The more the tester knows about the product and different test methods, the better the testing will be.

19

Exhaustive testing

Executing the program through all possible combinations of values for program variables.

20

Functional

Application of test data derived from the specified functional requirements without regard to the final program structure.

21

Incremental

adding unit-tested programs to a given
module or component one by one, and testing each resultant combination

22

Integration

first level of testing which formally integrates a set of programs that communicate among themselves via messages or files

23

Life Cycle Testing

The process of verifying the consistency, completeness, and correctness of software at each stage of the development life cycle.

24

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

25

Know the difference between all the different types of Analysis

1

26

Test cases

An individual test condition, executed as part of a larger test that contributes to the test’s objectives.

27

Use cases

technique for capturing the functional requirements of systems through the interaction between an Actor and the System.

Use Cases describe all the tasks that must be performed for the Actor to achieve the desired objective and include all of the desired functionality.

28

Test Stories

1

29

Test Data Sets

Set of input elements used in the testing process.

30

Test Item

Identify the items or features to be tested by this test case.

31

Test Plan

A document describing the intended scope, approach, resources, and schedule of testing activities. It identifies test items, the features to be tested, the testing tasks, the personnel performing each task, and any risks requiring contingency planning.

Contract / Roadmap

32

Test harness

A collection of test drivers and test stubs.

Utilized when other related code has not yet been completed but testing must proceed.

33

Test driver

A program that directs the execution of another program against a collection of test data sets. Usually, the test driver also records and organizes the output generated as the tests are run.

34

V-model

Demonstrates the relationships between each phase of development and its associated testing phase

Left = Specifications side
Right = testing side

35

Software Quality Criteria

1

36

Factors and Gaps

1

37

Understand the types of RISK, definitely a MUST KNOW

1

38

Quality Assurance

Support activities (facilitation, training, measurement, and analysis) needed to provide adequate confidence that processes are established and continuously improved to produce products that meet specifications and are fit
for use.

39

Quality Control

Process by which product quality is compared with applicable standards, and the action taken when nonconformance is detected. Its focus is defect detection and removal.

The performance of these tasks is the responsibility of the people working within the process.

40

Producer gap

Gap between what was specified to be delivered, and what was actually delivered.

41

Customer gap

Gap between customers expectations and the product delivered.