It helps prevent defects from being introduced into the code.

To identify defects in any software work product.

Risk-based testing is the term used for an approach to creating a test strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.

Risk-based testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations. In a decision table the inputs are listed in a column, with the outputs in the same column but below the inputs. The remainder of the table explores combinations of inputs to define the outputs produced.

Preventative tests are designed early; reactive tests are designed after the software has been produced.

It avoids author bias in defining effective tests.

The purpose of exit criteria is to define when a test level is completed.

The likelihood of an adverse event and the impact of the event determine the level of risk.

The likelihood of an adverse event and the impact of the event determine the level of risk.

The likelihood of level of risk and the impact of the event determine the level of risk.

Decision table testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations. In a decision table the inputs are listed in a column, with the outputs in the same column but below the inputs. The remainder of the table explores combinations of inputs to define the outputs produced.

Risk-based testing is the term used for an approach to creating a test strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.

To identify defects in any software work product.

To test defects in any software work product.

A. Test Implementation and execution

B. Test Analysis and Design

C. Evaluating the Exit Criteria and reporting

D. Test Closure Activities

i. Developing and prioritizing test cases, creating test data, writing test procedures and optionally preparing the test harnesses and writing automated test scripts.

ii. Creating the test suite from the test cases for efficient test execution.

iii. Verifying that the test environment has been set up correctly.

iv. Determining the exit criteria.

i. Test Items

ii. Test Scripts

iii. Test Deliverables

iv. Responsibilities

a) 17

b) 19

c) 24

d) 21

a) 22,23,26

b) 21,39,40

c) 29,30,31

d) 0,15,22

a) static testing requires the running of tests through the code

b) static testing includes desk checking

c) static testing includes techniques such as reviews and inspections

d) static testing can give measurements such as cyclomatic complexity

i. Helps to check the Quality of the built product

ii. Helps to check that we have built the right product.

iii. Helps in developing the product

iv. Monitoring tool wastage and obsoleteness.

i. Unit Testing

ii. Program Testing

iii. Module Testing

iv. System Component Testing .

a) Component Integration testing

b) Component System Testing

c) Component Sub System Testing

d) Maintenance testing