Here at mabl, we are always guess about better slipway to help you increase your test coverage. We believe that tryout creation should be seamless and tests should evolve alongside your app. As the scenarios available to your users become more complex, mabl simplify the process of creating tests that are both reusable and versatile.

Data-driven testingis one of the well-nigh potent puppet in your fixation examine toolbox. In bit, you can increase the coverage that an automated test provides by an order of magnitude; just replace your hard-coded values with variables, link the test to a datatable, and let mabl address the rest. Let ’ s walk through a simple example.

Using variables and datatables

Let ’ s begin with a test that call a website and search for occupation using a hard-coded keyword, “ engineer ”, and asserts that there should be some number of openings.
While this is a good offset, there are early job opening usable here. I ’ d like to verify that the search page works with different character of opening, not merely “ engineer ”, without creating a new test for each type.

I start by creating a new variable, “ Job_Type ”, which I ’ ll set via a new data rootage.

Next, I edit the footstep that enters the text to use the new “ Job_Type ” variable rather than the existing hard-coded string and save the test.

From the tryout details page within the mabl app, I then generate a new datatable. I define all the scenario that I require to test and I save the datatable.

Finally, I run the test using the new datatable.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Success! I can see that mabl correctly utilise the datatable to test each of the scenarios in parallel. From this screen stroke, for example, you can see that mabl successfully searched for and found a “ merchandising ” persona.

Parameterize steps and reuse datatables

In practice, your scenarios are probably more complex. Fortunately, you can pass your test and datatable to parameterize extra steps. You can also reuse datatables across many tests and even upload your existing data.

As always, we commend from there. Whether you ’ re a veteran automation technologist, a QA engineer, or a manual tester making the transition to low-code test automation, we hope this example helps you get start on the path to improve coverage by desegregatedata-driven testinginto your regression suite.

Sign up for a free trial of mablto get started establish your data-driven tests today.