lookidiet.blogg.se

• CAUSE AND EFFECT DIAGRAM SOFTWARE DEVELOPMENT CODE

OR - If any cause from C1 and C2 is true, then effect E1 will be true.

If both C1 and C2 are true, then effect E1 will be true. Notations used in the Cause-Effect GraphĪND - E1 is an effect and C1 and C2 are the causes. This technique aims to reduce the number of test cases but still covers all necessary test cases with maximum coverage to achieve the desired application quality.Ĭause-Effect graph technique converts the requirements specification into a logical relationship between the input and output conditions by using logical operators like AND, OR and NOT. The main advantage of cause-effect graph testing is, it reduces the time of test execution and cost. In this technique, the input conditions are assigned with causes and the result of these input conditions with effects.Ĭause-Effect graph technique is based on a collection of requirements and used to determine minimum possible test cases which can cover a maximum test area of the software. For example, while using email account, on entering valid email, the system accepts it but, when you enter invalid email, it throws an error message.

CAUSE AND EFFECT DIAGRAM SOFTWARE DEVELOPMENT CODE

The dynamic test cases are used when code works dynamically based on user input. Next → ← prev Cause and Effect Graph in Black box TestingĬause-effect graph comes under the black box testing technique which underlines the relationship between a given result and all the factors affecting the result.