Splitters Basics

The Tests Splitter, also known as Iterators, offers an efficient approach to simplify documentation tasks. Its primary function is to allow to document a Test one time but to know how many times it should be executed. This means that the number of test executions is not determined by the number of Tests documented, but rather by the number of Splitters defined for each test. Let's illustrate this with an example: Suppose we define a Splitter named "Browser" with the options: Chrome, Safari, Edge, and Firefox. Now, we create a Test and use the Browser Splitter options as shown in the image:

In this scenario, the system will understand that the Test should be executed four times, once for each browser selected. The executions will cover Chrome, Safari, Edge, and Firefox, as depicted in the image: