Testplace tutorials
  • Quality Assurance 101
  • Manual Testing
    • Manual Testing Tutorial
      • What is Software Testing?
      • Software Development Life Cycle
      • Software Testing Life Cycle
      • Types of Software Testing
      • Levels of Testing
      • Automation Vs Manual Testing
      • Black Box & White Box Testing
      • Smoke & Sanity Testing
      • Regression Testing
      • Retesting
      • Regression vs Retesting
      • Entry And Exit Criteria
      • Test Scenario vs Test Case
      • Manual Testing Methods
      • Verification and Validation
      • Test Strategy
      • Test Plan
      • Test Strategy vs Test Plan
      • Bug Report Template
      • Test metrics
      • Difference Between Defect Bug Error And Failure
      • Write Good Bug Report
      • Principles of Software Testing
      • Black Box Test Design Techniques
      • Equivalence Partitioning Testing Technique
      • Boundary Value Analysis Testing Technique
      • Decision Table Test Design Technique
      • State Transition Test Design Technique
      • Severity Vs Priority
Powered by GitBook
On this page

Was this helpful?

  1. Manual Testing
  2. Manual Testing Tutorial

Decision Table Test Design Technique

PreviousBoundary Value Analysis Testing TechniqueNextState Transition Test Design Technique

Last updated 5 years ago

Was this helpful?

Decision Table is aka Cause-Effect Table. This test technique is appropriate for functionalities which has logical relationships between inputs (if-else logic). In Decision table technique, we deal with combinations of inputs. To identify the test cases with decision table, we consider conditions and actions. We take conditions as inputs and actions as outputs.

Examples on Decision Table Test Case Design Technique:

Take an example of transferring money online to an account which is already added and approved.

Here the conditions to transfer money are ACCOUNT ALREADY APPROVED, OTP (One Time Password) MATCHED, SUFFICIENT MONEY IN THE ACCOUNT.

And the actions performed are TRANSFER MONEY, SHOW A MESSAGE AS INSUFFICIENT AMOUNT, BLOCK THE TRANSACTION INCASE OF SUSPICIOUS TRANSACTION.

Here we decide under what condition the action be performed Now let’s see the tabular column below.

In the first column I took all the conditions and actions related to the requirement. All the other columns represent Test Cases.

T = True, F = False, X = Not possible

From the case 3 and case 4, we could identify that if condition 2 failed then system will execute Action 3. So we could take either of case 3 or case 4

So finally concluding with the below tabular column.

From the case 2 and case 3, we could identify that if one of the condition failed then the system will display an error message as Invalid User Credentials.

So I am eliminating one of the test case from case 2 and case 3 and concluding with the below tabular column.