Software Testing Tutorial #36 - Decision Table Testing in Software Testing

Summary

This software testing tutorial introduces decision table testing, also known as cause-effect table testing, a technique used in black box testing for scenarios with multiple outcomes based on various conditions. The video explains how to use decision tables, typically created in Excel or Confluence, to ensure comprehensive testing of software functionalities like website registration, where success or error messages depend on multiple inputs. It demonstrates how to systematically cover all possible scenarios and validate the corresponding messages, providing a clear method to achieve thorough test coverage.

Takeaways

• 📘 Decision table testing, also known as cause-effect table, is a software test design technique used in black box testing for scenarios with multiple outcomes based on various conditions.
• 🔍 It is particularly useful for business rule testing where outcomes are determined by multiple conditions and is an alternative to techniques like equivalence partitioning and boundary value analysis.
• 📝 The method is employed when dealing with complex rules involving multiple components, such as different discount percentages for new and existing users.
• 📋 A decision table is typically created using tools like Excel or Confluence, and it helps in systematically covering all possible scenarios for testing.
• 🔑 The table is structured with columns representing different combinations of input conditions and rows for each test case, ensuring comprehensive coverage of potential outcomes.
• 📑 Inputs are categorized into mandatory fields, such as name, email, and address in a registration form example, which determine the success or failure of an operation.
• ✅ The table includes 'success message' and 'error message' columns to define the expected feedback for each combination of input values.
• 📝 Error messages in the table are derived from business requirements and should be specific to the missing or incorrect input values.
• 🔄 Each row in the decision table represents a unique test case that needs to be executed to verify the software's response to various input combinations.
• 📊 The decision table provides a clear and organized approach to test different scenarios, improving the overall test coverage and ensuring that all possible user interactions are considered.
• 💡 Understanding and applying decision table testing can be beneficial for cracking interviews and effectively testing software in a professional setting.

Q & A

What is Decision Table Testing also known as?

Decision Table Testing is also known as Cause Effect Table Testing.

What type of testing is Decision Table Testing considered to be?

Decision Table Testing is a software test design technique used in black box testing.

When is Decision Table Testing most useful?

Decision Table Testing is most useful when there are multiple outcomes based on various conditions that need to be tested, especially in business rule testing scenarios.

Can you give an example of a situation where Decision Table Testing would be applied?

An example would be testing a discount rule in an e-commerce application where the discount percentage might vary based on whether the user is new or existing, combined with other components.

What are the three mandatory fields mentioned in the registration example of the script?

The three mandatory fields for registration mentioned are name, email, and address.

How many combinations of inputs are there for the three mandatory fields in the registration example?

There are eight possible combinations of inputs for the three mandatory fields.

What tool is commonly used to create a Decision Table?

Excel or tools like Confluence are commonly used to create a Decision Table.

What should be the outcome if all three mandatory fields are provided during registration?

If all three mandatory fields are provided, the customer should receive a success message indicating a successful registration.

What should the tester do if the customer hasn't provided the name but has provided email and address?

In this case, the tester should expect no success message and an error message indicating that the name is missing.

How does a tester use the Decision Table to create test scenarios?

A tester uses the Decision Table to identify all possible combinations of inputs and their expected outcomes, turning these into test cases to verify the software's behavior.

What is the purpose of creating a Decision Table in software testing?

The purpose of creating a Decision Table is to ensure comprehensive test coverage by systematically testing all possible scenarios based on the defined rules and requirements.