Decision Table Testing

If three values are possible, the pattern repeats itself every three columns. One of the most important test goals for your project is to have 100% decision coverage. Therefore, we have to execute the following three tests for the control flow graph shown below. Subsequently, let’s have a look at these steps based on the above scenario. The usefulness and efficiency of this testing approach may be realized by
proceeding to the next level of collapsible decision-making table. Based on the given data, we can develop 8 separate test cases to assure
comprehensive coverage for this condition.

Another way to reduce the table is by checking for invalid combinations; for example, there is no way someone can be a Male and a Female in a decision table. Of course, in decision tables, we can use Yes/No or True/False – which are analogous to 0/1 values. We can use number value (for example, temperature), words, or pictograms (or whatever we need).
Failed software is sent back to the development team to fix the defect. Decision tables are a robust specification-based testing technique that can work for many scenarios. The tabular and the graphical representation is very beneficial for all stakeholders and non-technical members to understand easily. A decision table is a tabular representation of inputs vs cases, rules and test conditions. LambdaTest is an AI-powered test orchestration execution platform that allows the execution of both manual and automation tests across an online browser farm of 3000+ browsers, devices, and OS combinations.

Software engineering benefits

We can conclude that using Decision Tables proves to be a fundamental technique in Software testing. It is a technique that not only the testers can use but can also be utilized by anyone to break down any complex requirement with just a straightforward table of input combinations vs. expected results. This decision table is mainly specialized in the optimization of test cases as it allows a reduction in the number of test cases for better test coverage. This can be done while still testing crucial combinations of conditions. The third point is that although decision tables are definitely useful, this example system would be modelled well by a simple state machine.
Learn more about the education system, top universities, entrance tests, course information, and employment opportunities in USA through this course. Learn more about the education system, top universities, entrance tests, course information, and employment opportunities in Canada through this course. For more information on this, refer to “N-wise testing” in “Orthogonal arrays and pairwise testing” and to books on theory, such as [Copeland, 2003]. The initial step in constructing a table is pinpointing and defining the problem. This involves recognizing the relevant factors and determining the necessary next steps. Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.
decision table testing
Earlier this year, I was presented with a complex scenario where ten conditions would interact with one another. My challenge was to intelligently cull those one hundred test cases to a more reasonable number. Looking at the full sixteen combinations we identified, we can now cut those down by eliminating redundant conditions and impossible conditions. Invalid combinations are those that cannot happen, for example, that someone is both an infant and senior.

Tools for Creating Decision Tables

The general shape of a decision table after step 2 – “Creating logical test cases” is shown in the table below. Using decision tables is not always easy, but in my experience, the results reaped from the exercise are always worth the effort. Try this technique to make your test design process more efficient, effective, and understandable. The condition alternatives are simple Boolean values, and the define decision table action entries are check-marks, representing which of the actions in a given column are to be performed. Decision tables are a concise visual representation for specifying which actions to perform depending on given conditions. The information expressed in decision tables could also be represented as decision trees or in a programming language as a series of if-then-else and switch-case statements.
decision table testing
In logical test cases, they occur in several rows, while that particular data naturally only occurs once in the table for physical test cases. Besides this, it is possible that additional refinements are required. For example, by putting derived data into concrete terms (see example below).

Therefore, we should always use it with boundary value and Equivalence partitioning techniques wherever possible. Consider a Banking application that will ask the user to fill a personal loan application online. Based on the inputs, the application will display real-time whether the loan will get approval, rejection, or requires a visit to the branch for further documentation and discussion. In addition to this, we won’t change it to reduce the complexity of this scenario. If any of the requirements are not satisfied, the system will display an error

  • In the example used here, we were able to cut the number of test cases from sixteen down to just five—a reduction of nearly 70 percent!
  • To conclude, we have seen that Decision table testing is immensely beneficial when we have to test complex business rules.
  • Here, input denotes the factors or conditions needed to evaluate the behavior of the software application.
  • Using decision tables is not always easy, but in my experience, the results reaped from the exercise are always worth the effort.

notice describing the problem, and if all conditions are met, the photo will

be correctly updated.
decision table testing
In the example, this condition could be included in respect of the number of capsules and the distance. However, it has some notable drawbacks, such as increased time consumption, potential security and performance scanning issues, and the requirement for expert testers to maintain the tables. Despite these drawbacks, decision table testing is highly recommended, given its ability to provide comprehensive coverage for different scenarios.