Without a single line of code AI-Assisted Capture Web, Mobile, and APIs

Create an automated test without writing code

There are two ways to build a scenario: you navigate through it and the AI writes it, or you assemble it using action blocks. In either case, no one on the team needs to know how to code.

app.mrsuricate.com

Script in progressRecording in progress

WebsiteMobile appAPI

Block ·Go to the home pageCaptured
Block ·Log inCaptured
Block ·Add to CartTo be completed
Block ·Check the amountCaptured

Last run 4 minutes ago

Saved script6 blocks, no lines of code

A test written in code belongs only to the person who wrote it

A Selenium, Cypress, or Playwright script becomes unreadable to the rest of the team as soon as its author leaves. And as long as its creation depends on a single developer, test coverage progresses at the pace of sprint priorities—which means slowly.

AI-Assisted Capture

You navigate through your app as usual. The AI observes your interactions and builds the corresponding scenario, which you then review and adjust.

Block Assembly

Each user action is a block: clicking, typing, navigating, waiting, checking. You link them together in the order of the actual user journey.

Reusable blocks

Logging in, adding an item to the cart, or submitting a form become blocks shared across multiple scenarios.

Explicit Checks

A test that doesn't verify anything doesn't prove anything. You place the checks where they matter: the amount, the confirmation message, and the email received.

What does a scenario actually look like?

A six-step purchasing journey, as it is built in the editor. No lines of code, and each step remains clear six months later.

The blocks you're putting together

A scenario is a sequence of blocks. Each block corresponds to an action that a real user would perform.

Click and double-click
Text Entry
Navigation and URLs
Conditional Pending
Selecting from a list
File Upload
Text Verification
Element Verification
Reusable pad

A script that the entire team can understand, that can be modified without a developer, and in which each block can be reused elsewhere.

SCENARIOPurchasing a Product Online

1Go to/collections/nouveautes
2Click onAjouter au panier
3Sign in withun compte de test
4Fill in the fieldCode promo
5Check that the amount49,90 €
6Check that the textCommande confirmée

6 reusable blocks assembled without codethat can be reused in your other scenarios

GO FURTHER

Maintaining Your Test CasesSelf-healing of selectors and shared blocks, so that coverage remains consistent over time.All FeaturesThe seven building blocks of the platform, from scenario creation to execution verification.The 14 types of testsWhat you can automate, grouped by category and priority.

YOUR QUESTIONS

Questions We Get Asked About the Publisher

Creation, AI-powered data capture, relevant profiles: answers to the most frequently asked questions.

Do you need to know how to code to create a test?

No, and that's the point. Not to create a scenario, not to modify it, and not to review it. The blocks describe user actions, not code.

What exactly does the journey capture AI do?

It observes your interactions as you navigate through your app and derives the corresponding sequence of blocks. You're in charge of reviewing and fine-tuning the results.

Who can create a test within the team?

QA, product, business, and IT teams all work on the same platform, using the same building blocks. This is what allows test creation to extend beyond the scope of developers alone.

How can a script remain readable six months from now?

Each block has a clear label, and repeated actions are grouped into reusable blocks. A scenario reads like a series of steps, not like a script.

Where can I find details about the parameters for each block?

In the product documentation, which remains the definitive reference for options, selectors, and special cases. This page describes the value and how it works, not the configuration.