In this section, we are going to see how to make database tables act as data sources for our tests. The previous examples revolved around one-level tests where none of them involved the Test as step feature. In contradiction, we are going to walk through three scenarios that use two-level tests. They will highlight how Test Studio interprets the execution of two embedded tests where at least one of them is data-driven. The cases we are going to tackle are as follows:
Outer test is a regular test and comprises a data-driven embedded test
Outer test is data-driven and comprises a regular test
Outer test is data-driven and comprises also a data-driven test
Each of the preceding approaches is going to be demonstrated in the right context where we will see how to implement them and how they will execute.