Types of Tests

Functional Testing: Make Sure Your User Flows Actually Work

A form that no longer submits, a flow that gets stuck at step 3, a button that no longer works. Functional tests replay your critical user flows with every release—on the web, on mobile, and across your APIs.

Without writing any codeWeb, Mobile, and APIsHosting in the EU

Scenario Management in Mr Suricate : Successes, Failures, Related Incidents, and Planning

They trust us

3 million scenario runs per month100+ clients15 types of tests covered

Retail, banking, manufacturing, transportation, services. Hosting in the European Union, French-language support, personalized assistance during the startup phase.

In a nutshell

A functional test verifies that a workflow does what it's supposed to do from the user's perspective: a form is submitted, a shopping cart is updated, or an account is created. Run automatically with each release—on the browser, on mobile, and via APIs—it flags any discrepancies between expected and actual behavior.

A challenging course doesn't give you any warning

A production release passes the unit tests, the code is clean, and yet the contact form hasn’t been sending anything for three days. No one noticed, because no one manually reviews the app’s fifty user flows with each release. Automated functional testing does exactly that: it replays the user flow just as a user would, and alerts you as soon as the result changes.

The course played from start to finish

Clicks, keystrokes, uploads, page transitions. The scenario replicates what a real user does in a real browser.

The Checks That Matter

Text displayed, amount calculated, email received, redirect completed. You decide what should be true at each step.

Across all your environments

Recipe, pre-production, production. Variables and datasets by environment, without duplicating the scenario.

Without writing a single line of code

AI-assisted data capture or block-based assembly. A business profile that builds and refines its own scenarios.

Relive your runs without having to reconfigure your setup

Your functional tests are triggered from your CI, run on your production environments, and report back to where your teams are already working. No need to retool.

1 Triggering Your tools stay in control

GitLab
Jenkins
Microsoft Azure
API Call
Planning

2 Execution

Your scripts run on your production environments

Web Tour
Native iOS and Android Apps
Real Mobile Farms
APIs and Internal Feeds

3 Restitution The results are delivered right to your workplace

Jira
Slack
SMS
Webhook
API

And maintenance that stands the test of time

Reusable blocksA change updates all scenarios that use it
AI-Assisted CorrectionSuggested corrections for scenarios with errors
Grouping IncidentsSimilar anomalies are processed only once

How Automation Is Changing Things, Line by Line

Manual Functional TestingWith Mr Suricate

Manual Functional Testing

With Mr Suricate

A full-scale campaign keeps the team busy for an entire day.

The same ad runs for a few minutes.

We test whatever we have time to test before going live.

All critical paths are checked with every delivery.

The result depends on who did the testing and how tired they were.

The same script returns the same result every time it runs.

A regression is discovered by a dissatisfied customer.

The failure is logged in Slack or Jira within a minute.

Replaying a course on four browsers takes four times as long.

Browsers and resolutions are handled in parallel.

The proof of the test is a checked box in a spreadsheet.

Each step is time-stamped, recorded, and can be replayed.

Result200 scenarios played out in 3 minutes, and zero lines of code needed to build them.

No-Code Scenario

Written using capture or in blocks, reviewed by a business profile

Modified without changing the code, including by someone else

Can be exported to Playwright if you decide to leave

Recorder only

Very quick to produce

Break at the first gear shift

Not very reusable from one course to another

Homemade script

Total flexibility

A developer on hand for every update

Maintenance falls to the team that delivers

assertion, test case, false positive: the definitions are in the QA glossary.

WHITE PAPER · TEST AUTOMATIONWhat if your bugs no longer cost your business anything?The true cost of bugs, the fundamentals of testing before automation, and how to build a strategy that stands the test of time.

Download the white paper

“What convinced me was the no-code approach: our QA engineer got the hang of the tool in just a few days. The tangible result: fewer bugs in production and smoother deployments.”

Arnaud TrotignonCTO, Optivalue

You can keep control, or you can let us take charge

With Mr Suricate, your QA team isn't replaced—it's strengthened. You choose what to handle in-house and what to outsource: creating test scenarios, running them, or maintaining them over time.

1Identification of critical paths, front-end and back-end
2Writing Tests Without Code
3Continuous monitoring and alerts
4Scenario Maintenance and Development

ResultYou gain broader coverage without increasing your teams’ workload. And if you’d rather delegate everything, QA outsourcing takes over.

GO FURTHER

Other Types of Tests

Fifteen types of tests, four categories. Each one answers a different question about your application.

Non-regression testingRe-run all validated test cases before each production release to verify that a change hasn’t broken anything.Learn more End-to-End TestingThe complete user flow, from start to finish, including third-party systems and back-office systems.Learn more API testingCommunications between your services, tested directly without going through the interface.Learn more Performance TestingThe actual response time of your workflows, continuously measured and compared to your thresholds.Learn more Visual testingPixel-by-pixel visual comparison for changes that no assertion can detect.Learn more Accessibility testingAutomatically verifies that user flows comply with accessibility criteria.Learn more Security testingCheck what a user can actually access: permissions by profile, sessions, authentication, HTTPS.Learn more The 15 types of testsThe big picture: four categories, fifteen types, and where to start based on your situation.Learn more

Is there a term you don't understand? The automated testing glossary defines it.

YOUR QUESTIONS

Frequently Asked Questions

The questions QA teams ask us most often about functional testing.

What is a functional test?

A functional test verifies that a feature produces the expected result from the user's perspective. It does not examine how the code is written, but rather what the application displays and does: the account is created, the amount is correct, the email is sent, and the next page is displayed.

How is this different from a non-regression test?

It's the same scenario, run at a different time and for a different reason. A functional test verifies that a feature works. A regression test re-runs all the scenarios that have already been validated to verify that a change hasn't broken anything else.

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

No. Scenarios are built using assisted recording or by assembling blocks, without writing any code. This is what allows a business analyst or a non-developer tester to create and update their own tests.

How many scenarios do you need to get started?

About ten critical test scenarios are enough to cover the bulk of the risk: login, search, order flow, contact forms, and payment forms. Coverage is then expanded as the system evolves, without having to start from scratch.

Are mobile apps covered?

Yes, in both senses of the word. Real iOS and Android apps are run on farms of actual devices, and your web journeys are also tested at your users' mobile resolutions.

Does automated functional testing replace manual acceptance testing?

No. It handles the repetitive tasks—that is, the workflows your teams repeat with every release. Manual acceptance testing handles what a machine can’t do: exploration, business judgment, and validation of design intent.

What happens when the interface changes?

Two mechanisms help minimize damage. First, reusable blocks: a change updates all scenarios that use that block. Second, AI-assisted repair, which suggests fixes when a selector has moved. Validation is still done by humans.

How long before the first results?

A few days. There’s no need for any preliminary integration work, and it’s not tied to a specific release: the initial scenarios are built around your application as it is currently live.

Are APIs and mobile apps covered?

Yes, for the web, native iOS and Android apps on actual mobile devices, and internal APIs and feeds. Thick clients are not supported.

How is this different from a unit test?

A unit test verifies a single function—written by a developer—without a browser. A functional test simulates the entire user journey in a real browser, from the user's perspective. The two complement each other: the former catches a calculation error, while the latter catches a form that no longer submits anything.

No-code or low-code—what's the difference in practice?

No-code allows you to build applications without writing code, either by dragging and dropping or by assembling blocks. Low-code still requires a few lines of code for special cases. Here, the scenario can still be managed by a business user, and it can be exported to Playwright by a developer who prefers to work in their editor.

Do you only believe what you see?

A 30-minute demo of your own app. You'll see one of your workflows automated in real time, without writing any code.