Télécharger la présentation
## Overview

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -

**ECE 453 – CS 447 – SE 465 Software Testing & Quality**AssuranceLecture 7InstructorPaulo Alencar**Overview**• Functional Testing • Boundary Value Testing (BVT) • Boundary Value Analysis • Robustness Testing • Worst Case Testing • Special Value Testing • Equivalence Class Testing • Weak Equivalence Class Testing • Strong Equivalence Class Testing • Traditional Equivalence Class testing • Decision Table Based testing • Decision Tables • Technique • Examples**Decision Tables - General**Decision tables are a precise yet compact way to model complicated logic. Decision tables, like if-then-else and switch-case statements, associate conditions with actions to perform. But, unlike the control structures found in traditional programming languages, decision tables can associate many independent conditions with several actions in an elegant way.**Decision Tables - Usage**• Decision tables make it easier to observe that all possible conditions are accounted for. • Decision tables can be used for: • Specifying complex program logic • Generating test cases (Also known as logic-based testing) • Logic-based testing is considered as: • structural testing when applied to structure (i.e. control flow graph of an implementation). • functional testing when applied to a specification.**Decision Tables - Structure**• Each condition corresponds to a variable, relation or predicate • Possible values for conditions are listed among the condition • alternatives • Boolean values (True / False) – Limited Entry Decision Tables • Several values – Extended Entry Decision Tables • Don’t care value • Each action is a procedure or operation to perform • The entries specify whether (or in what order) the action is to be • performed**Condition entry**• To express the program logic we can use a limited-entry decision table consisting of 4 areas called the condition stub, condition entry, action stub and the action entry: Condition stub Action stub Action Entry**We can specify default rules to indicate the action to be**taken when none of the other rules apply. • When using decision tables as a test tool, default rules and their associated predicates must be explicitly provided.**Decision Table - Example**Printer Troubleshooting**Decision Table Development Methodology**• Determine conditions and values • Determine maximum number of rules • Determine actions • Encode possible rules • Encode the appropriate actions for each rule • Verify the policy • Simplify the rules (reduce if possible the number of columns)**Decision Tables - Usage**• The use of the decision-table model is applicable when : • the specification is given or can be converted to a decision table . • the order in which the predicates are evaluated does not affect the interpretation of the rules or resulting action. • the order of rule evaluation has no effect on resulting action . • once a rule is satisfied and the action selected, no other rule need be examined. • the order of executing actions in a satisfied rule is of no consequence. • The restrictions do not in reality eliminate many potential applications. • In most applications, the order in which the predicates are evaluated is immaterial. • Some specific ordering may be more efficient than some other but in general the ordering is not inherent in the program's logic.**Decision Tables - Issues**• Before using the tables, ensure: • rules must be complete • every combination of predicate truth values plus default cases are explicit in the decision table • rules must be consistent • every combination of predicate truth values results in only one action or set of actions**Test Case Design**• Once the specification has been verified, the objective is to demonstrate that the implementation provides the correct action for all combinations of predicate values: • if there are k rules over n binary predicates, then there are at least k cases and at most 2n cases to consider. • Base test design on unexpanded rules or on the expanded rules with 2n tests • find the input vector to force each case.**Test Case Design**• To identify test cases with decision tables, we interpret conditions as inputs, and actions as outputs. • Sometimes conditions end up referring to equivalence classes of inputs, and actions refer to major functional processing portions of the item being tested. • The rules are then interpreted as test cases.**Decision Table for NextDate(First Attempt)**• Let us consider the following equivalence classes: M1= {month | month has 30 days} M2= {month | month has 31 days} M3= {month | month is February} D1= {day | 1 ≤ day ≤ 28} D2= {day | day = 29} D3= {day | day = 30} D4= {day | day=31} Y1= {year | year = 1900} Y2= {year | 1812 ≤ year ≤ 2012 AND year ≠ 1900 AND (0 = year mod 4} Y3= {year | 1812 ≤ year ≤ 2012 AND 0 ≠ year mod 4}**Decision Table for NextDate(Second Attempt)**• Let us consider the following equivalence classes: M1= {month | month has 30 days} M2= {month | month has 31 days} M3= {month | month is December} M4= {month | month is February} D1= {day | 1 ≤ day ≤ 27} D2= {day | day = 28} D3= {day | day = 29} D4= {day | day = 30} D5= {day | day=31} Y1= {year | year is a leap year} Y2= {year | year is a common year}**Guidelines and Observations**• Decision Table testing is most appropriate for programs where • there is a lot of decision making • there are important logical relationships among input variables • There are calculations involving subsets of input variables • There are cause and effect relationships between input and output • There is complex computation logic (high cyclomatic complexity) • Decision tables do not scale up very well • Decision tables can be iteratively refined