Chapter 1

Question 1

Coverage

Answer 1

The degree to which specified coverage items have been determined or have been exercised by a test suite expressed as a percentage.

Question 2

Debugging

Answer 2

The process of finding, analyzing and removing the causes of failure in software,

confirmation testting checks whether the fixes resolved the defects

Question 3

Defect

Answer 3

An imperfection or deficiency in a work product where it does not meet its requirements or specifications. This may cause a failure but not in all circumstances. It may require specific inputs or preconditions.

Question 4

Error

Answer 4

A human action that produces an incorrect result

Question 5

Failure

Answer 5

An event in which a component or system does not perform a required function within specified limits

Question 6

Quality

Answer 6

The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.

Question 7

Quality Assurance

Answer 7

Part of quality management focused on providing confidence that quality requirements will be fulfilled

Question 8

Root Cause

Answer 8

A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.

Question 9

Test analysis

Answer 9

The activity that identifies test conditions by analyzing the test basis.

The process of transforming defined test objectives into tangible test conditions and test cases.

Question 10

Test basis

Answer 10

The body of knowledge used as the basis for test analysis and design.

Question 11

Test case

Answer 11

A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.

Question 12

Test completion

Answer 12

The activity that makes test assets available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders.

Question 13

Test condition

Answer 13

An aspect of the test basis that is relevant in order to achieve specific test objectives

Question 14

Test control

Answer 14

A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned.

Take necessary actions to get testing back on track

Question 15

Test data

Answer 15

Data created or selected to satisfy the execution preconditions and inputs to execute one or more test cases.

Question 16

Test design

Answer 16

The activity of deriving and specifying test cases from test conditions.

Question 17

Test execution

Answer 17

The process of running a test on the component or system under test, producing actual result(s).

Question 18

Text execution schedule

Answer 18

A schedule for the execution of test suites within a test cycle

Question 19

Test implementation

Answer 19

The activity that prepares the testware needed for test execution based on test analysis and design

Question 20

Test monitoring

Answer 20

A test management activity that involves checking the status of testing activities, identifying any variances from the planned or expected status, and reporting status to stakeholders.

running reports, reviewing reports

Question 21

Test object

Answer 21

The component or system to be tested

Question 22

Test objective

Answer 22

A reason or purpose for designing and executing a
test, ie
prevent defects
Validation of User Requirements
Verification of fulfillment of requireemnts
Build Confidence in Level of Quality
Compliance

Question 23

Test oracle

Answer 23

A source to determine expected results to compare with the actual result of the system under test.

Question 24

Test planning

Answer 24

The activity of establishing or updating a test plan.

Question 25

Test procedure

Answer 25

A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post execution

Question 26

Test process

Answer 26

The set of interrelated activities comprising of test planning, test monitoring and control, test analysis, test design, test implementation, test execution, and test completion. Activities are not necessarily sequential (iterative/overlap) Context matters in determining test process: testing for a research POC vs a Medical Device.

Question 27

Test suite

Answer 27

A set of test cases or test procedures to be executed in a specific test cycle

Question 28

Testing

Answer 28

The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation, and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate they are fit for purpose and to detect defects. (test planning, test analysis, test design, test implementation, test reporting, test evaluation, test execution)

Question 29

Testware

Answer 29

Work products produced during the test process for use in planning, designing, executing, evaluating, and reporting on testing.

Question 30

Traceability

Answer 30

The degree to which a relationship can be established between two or more work products

Question 31

Validation

Answer 31

Confirmation by examination and through provision of objective evidence that the requirements for a specific intending use or application have been fulfilled. Comparing work product to actual user needs (acceptance testing). Dynamic Testing.

Question 32

Verification

Answer 32

Confirmation by examination and through provision of objective evidence that specific requirements have been fullfilled. Comparing the work product of one level to the previous one (User requirements, software requirements, architecture, design). Also check each work product for consistency, completeness. Static analysis and testing techniques walkthroughs, inspections, traceability.

Question 33

Difference between Validation and Verification

Answer 33

System will meet user and other stakeholder needs (Dynamic) vs System performs as per specified requirements (Static)

Question 34

Testing

Answer 34

test planning, test analysis, test design, test implementation, test reporting, test evaluation, test execution

Question 35

Static Testing

Answer 35

Testing a work product without code being executed

Question 36

Dynamic Testing

Answer 36

Testing that involves the execution of the software of a component or system

Question 37

Role of Testing

Answer 37

Reduce risk of failures or the occurrence of problems during operation. Contribute to overall quality of software. Increase likelihood of meeting statekholder needs.

Question 38

Quality Assurance

Answer 38

Adherence to proper processes in order to provide confidence that the appropriate level of quality will be achieved.

Question 39

Quality Management

Answer 39

Activities that direct and control an organization with regard to quality. Includes both Quality Assurance and Quality Control.

Question 40

Quality Control

Answer 40

Activities that support the achievement of appropriate levels of quality, including test activities.

Question 41

Error vs Defect vs Failure

Answer 41

Person vs Code/Work Product vs Execution

Question 42

Root cause

Answer 42

Source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.

Question 43

Testing Principle 1

Answer 43

Testing shows the presence of defects, not their absence

Question 44

Testing Principle 2

Answer 44

Exhaustive testing is impossible (except in trivial cases)

Question 45

Testing Principle 3

Answer 45

Early testing saves time and money - begin with the requirements

Question 46

Testing Principle 4

Answer 46

Defects can cluster - a few modules will have the most defects, and testing should be focused appropriately

Question 47

Testing Principle 5

Answer 47

Pesticide Paradox, running the same tests over and over will eventually not find defects; the defects have been romoved.

Question 48

Testing Principle 6

Answer 48

Testing is context dependent; what you test and how thoroughly you test it varies depending on the risk and life cycle. (safety critical vs consumer app)

Question 49

Testing Principle 7

Answer 49

Absence of errors is a fallacy fixing all the located defects does not guarantee the software will work or meet user needs. Just finding and fixing a large number of defects will ensure the success of a system.

Question 50

Exhaustive Testing

Answer 50

A test approach in which the test suite comprises all combinations of input values and pre-conditions (13 fields with 3 values yields 3xx13 or 1,594,323 tests

Question 51

Test Analysis Steps

Answer 51

``` Step 1: identify the test basis Step 2: evaluate for defects Step 3: identify features to be tested Step 4: design and prioritize test conditions Functional, Non Functional, Structural, Experience Based, Other Business and technical factors, Risk Step 5: bidirectional traceability between basis and conditions ```

Question 52

Test Analysis Defects

Answer 52

``` Ambiguities Omissions Inconsistencies Inaccuracies Contradictions Superfluous statements ```

Question 53

Test Design Tasks

Answer 53

Prioritize High Level Test Cases Identify Necessary Test Data Specify Test Environment Set-up, including tools and infrastructure Ensure traceability between test basis, conditions, and cases Find defects in test basis

Question 54

Test Implementation Tasks

Answer 54

``` Implement and prioritze test cases Develop and prioritze test procedures Create Test Data Organize into suites, execution schedule Build and verify test environment Update and verify bidirectional traceability ```

Question 55

Test Execution Tasks

Answer 55

``` Record versions of items, objects, tools, testware used Execute manual / automated tests Compare actual v expected Analyze causes of anomalies Log outcome of executions (pass/fail/blocked) Report defects Re-execute failed test Verify traceability ```

Question 56

Test Completion Tasks

Answer 56

``` Lessons Learned Turnover Planned Deliverables Closure of Defect Reports Create Test Summary Finalizing testware for later user Improve Test Process ```

Question 57

Test Monitoring and Control Work Products

Answer 57

Test Progress Reports | Test Summary Reports

Question 58

Test Analysis Work Products

Answer 58

Test Conditions Traced to Test Basis Prioritized Test Conditions Defects

Question 59

Test Design Work Products

Answer 59

HL Test Cases Test Data Test Environment

Question 60

Test Implementation Work Products

Answer 60

``` Test Data Test Cases Test Procedures Test Suites Test Execution Schedule ```

Question 61

Test Execution Work Products

Answer 61

Test Case/Procedure Status Test Logs Defect Reports

Question 62

Test Completion Work Products

Answer 62

``` Test Summary Report Closed Defect Report Action Items for Improvement Change Request / Backlog Items Finalized Testware ```