Equivalence Class Testing (ECT)
• It is Software Testing Technique – Divide input values into valid and invalid partitions and
selecting representative values from each portioned as test data
• Use of ECT :
• Exhaustive testing is desired
• To avoid redundancy
• Type of ECT
• Weak Normal ECT
• Strong Normal ECT
• Weak Robust ECT
• Strong Robust ECT
Example for ECT
Advantages :
Helps to reduce the number of test cases
Reduces the test execution time ( minimize the set of test data)
Disadvantages :
Not contain any conditions for boundary value
Identifying the equivalence class relay on testers expertise
Other Names for Black box Testing
• behavioral, opaque-box, closed-box, specification-based, or eye-to-
eye testing.
State Table based Testing
• Table is tool for representing and documenting many types of information
relating to test case design.
• State Table : a tabular representation of a state graph (All states, inputs,
transitions and outputs )
• State based Test : Whether the software under test (SUT) returns the right
result, or modifies state correctly.
• State-transition diagrams are very useful for describing the behavior of a
system and are part of the Software Design Document.
• Real-time Example : Embedded software industry and technical automation,
internet applications or business scenarios
Examples :State Table based Testing (ATM Card)
The states that the software may occupy (funded/insufficient funds);
The transitions from one state to another (not all transitions are allowed);
The events that cause a transition (withdrawing money); –> Inputs
The actions that result from a transition (an error message, or being given your cash). –> Output
Decision Table (Cause Effect) Based
Testing
• Decision Table Testing is a Black Box test design technique (behavioral or
behavior-based technique), used where different combinations of test input
conditions result in different outcomes.
• DT consists of
• conditions and actions – True/ False
• Decision rules: True/ false
• The main and the most important objective of Decision table testing is to
ensure the overall test coverage without missing any possible relation.(Or)
• boundary values check is essential for DT (Equivalence Class and Boundary
value analysis )
Examples :Decision Table Cause Effect)
Based Testing
Here are the business rules.
• On entering correct combination of ID & Password, user should be able to login successfully.
• User is not allowed to login when any or both of the ID & Password are incorrect /blank. In such cases, it should show
‘Invalid Credentials’ message.
3 pow 2 = 9 Test Cases
1. conditions – User ID, Password
2 Actions – Login Successfully, Error
showing ‘Invalid Credentials’ and
3 Options — Blank, Valid, Invalid.