Selenium Framework Design in Data-Driven Testing

Common setup

The tricky part is where to create each instance of the driver, browser, or mobile. In this example, each <test> section will run in parallel. So, it would make sense to pull in the parameters defined in each section in the @BeforeTest section of the common setup class. That would include casting the properties file to a separate thread for just that instance.

Also, it is important to keep all the local variables defined in each test class private when running in parallel. They should only be available to that class instance so reassigning them in the test class doesn't interfere with the other parallel thread running.

Here's what the common setup class looks like for parallel testing at the <test> level:

public abstract class ...