Press Cmd/Ctrl + P and choose “Save as PDF” (landscape, no margins).
© 2026 Meticulous. All rights reserved.


Meticulous training
A working session on exhaustive, deterministic frontend testing for modern product teams.
© 2026 Meticulous. All rights reserved.

How Meticulous works
How to use Meticulous
Understanding the review process
Viewing your code coverage
Common misconceptions
Q&A
© 2026 Meticulous. All rights reserved.

How Meticulous works
Meticulous records user sessions on your application
Meticulous constantly selects and updates the set of user sessions that provide the highest level of coverage
Meticulous integrates directly with GitHub and your CI to trigger test runs whenever a new commit is pushed to an open PR
Meticulous surfaces any visual, logical or behavioural differences between the new and old versions of your app
© 2026 Meticulous. All rights reserved.

How Meticulous works
Meticulous injects a JavaScript snippet into the client side application that captures user behaviour
The data in these sessions include user events (clicks, keydowns, etc.), network activity, and browser metadata
When replaying the session, Meticulous simulates all user events in the same sequence they were recorded and takes screenshots at important moments

Example screen recording
© 2026 Meticulous. All rights reserved.

How Meticulous works
Meticulous automatically selects the set of sessions that provide the highest level of coverage on a daily basis
While automatic session selection is usually sufficient, you do have the ability to manually select any sessions. This ensures that they are executed on every test run. We don't advise doing this as it's an additional burden and adds limited value

Selected sessions
© 2026 Meticulous. All rights reserved.

How Meticulous works
Meticulous automatically initiates a test run for every new commit to a branch with an open Pull Request
Meticulous comments directly on Pull Requests with a link to view and potentially review any visual differences


© 2026 Meticulous. All rights reserved.

How Meticulous works
Meticulous automatically initiates a test run for every new commit to a branch with an open Pull Request
Meticulous comments directly on Pull Requests with a link to view and potentially review any visual differences

© 2026 Meticulous. All rights reserved.


© 2026 Meticulous. All rights reserved.

Sample PRs
© 2026 Meticulous. All rights reserved.

How to use Meticulous
The default grouping is Similar Differences, which groups the underlying elements that changed regardless of the screen the change occurred on. This allows you to typically only need to sample a small subset of the total differences

© 2026 Meticulous. All rights reserved.

How to use Meticulous

© 2026 Meticulous. All rights reserved.

How to use Meticulous

© 2026 Meticulous. All rights reserved.

How to use Meticulous
The drilldown view enables you to view more session specific functionality such as viewing the HTML difference, a full timeline, and replays of the simulations


© 2026 Meticulous. All rights reserved.

How to use Meticulous
Debug with AI initiates an agent debugger with full context on your code change and the session replayed, and provides a diagnosis of why a change happened

© 2026 Meticulous. All rights reserved.

How to use Meticulous
You can get your agents to communicate directly with Meticulous using our agentic skills. See the documentation for more information. This allows them to directly run test runs and check results to validate changes

© 2026 Meticulous. All rights reserved.

This difference is as expected based on the code change
The difference is not intended and is due to the code change and should be changed before merging the code
The difference doesn't appear to be a real difference related to the code change and shouldn't block merging the code
© 2026 Meticulous. All rights reserved.

You can find your latest code coverage for your project in the project overview section


Project Overview
© 2026 Meticulous. All rights reserved.

Meticulous will test my backend API endpoints
No, Meticulous automatically stubs out your backend APIs with the network responses recorded in the original session. It only tests frontend code and server side rendered pages
I need to rebase my branch to produce accurate test results
No, Meticulous should use the base commit of the Pull Request branch automatically. If you see diffs from commits that are not in your branch, it's a bug, so report it to the team
I shouldn't approve these differences because I'll break Meticulous
No, you cannot break Meticulous tests by approving a difference. Meticulous is self healing and you cannot break it by approving
© 2026 Meticulous. All rights reserved.


Deep dive
Meticulous Deep Dive at 3pm today in the Big Room
Need help?
Join the Meticulous Slack channel to report any bugs and ask for help