No production data Encrypted Secrets One scenario, multiple profiles

Feed data into your tests without affecting production

A scenario that repeatedly runs the same calculation eventually ceases to prove anything. Separate variables, datasets, and environments allow the same test to be run on different cases without duplicating it.

app.mrsuricate.com

Dataset4 profiles

WebsiteMobile appAPI

Profile 1 ·New CustomerPast
Profile 2 ·Loyal CustomerPast
Profile 3 ·Expired promo codeFailure
Profile 4 ·Empty CartPast

Last run 4 minutes ago

Borderline case detectedA single scenario replayed

The Single Test Account, and How Much It Costs

Two classic pitfalls. The first is using a single account for everything: the day that account gets blocked, the entire campaign goes down and the report becomes unreadable. The second is copying the production database into the staging environment, which solves the realism issue but creates a much bigger one related to GDPR.

Import File

Your datasets are provided as files. One row per case, one column per value that changes in the scenario.

PLC Power Supply

Data can also be fetched via an API call to refresh it before a campaign without requiring manual intervention.

Protected Data

An administrator marks data as protected: other users in the workspace cannot see it, and it does not appear in reports.

Variables by Environment

URLs, accounts, and keys vary depending on whether it's a test, pre-production, or production environment. The scenario, however, remains the same.

One scenario, multiple profiles

ProfileChanging dataExpected result

New CustomerShopping cart total: €49.90Order confirmed, email sent

Loyal CustomerValid promo codeDiscount applied, total recalculated

Empty CartNo itemsPayment button is inactive

Expired promo codeLast year's codeClear error message, shopping cart retained

One scenario, four lines in a file. That's what makes the difference between covering a path and covering its edge cases.

GO FURTHER

Create the scenarioAI-assisted capture or block-based assembly, without writing any code.Verify your analytics dataVerify that each event sent to GA4 contains the correct values.GDPR TestingVerify that no data is sent before the user gives consent.

YOUR QUESTIONS

Questions We Get Asked About Test Data

Data sources, confidential information, environments: answers to the most frequently asked questions.

Where does the data used in a scenario come from?

From three sources: a file you import, an API call that populates them before the campaign, or a dedicated workflow that creates them directly in your application, just as a user would.

Can we use production data?

It is possible, but we do not recommend it, unless the data was created by you specifically for testing purposes. Copying a production database to a test environment poses a GDPR risk that is not justified in this case.

Where are passwords and API keys stored?

Data is encrypted at rest and is never stored in plain text, either in an execution report or in an export. An administrator can also mark data as protected: other users of the workspace cannot see it.

How do I manage different URLs and accounts depending on the environment?

Through variables specific to each environment. The same scenario runs in testing, pre-production, and production without being duplicated or modified.

What happens if a test account is blocked?

The script fails, and that's the expected behavior: the report identifies the step and the data in question. That's precisely why we avoid basing an entire campaign on a single account.