Selecting Which Sessions to Run

Meticulous replays each session that gets recorded and tracks the characters of code executed, the components rendered, and the route patterns hit. Meticulous then continuously selects a combination of sessions that aim to collectively cover all of your distinct characters of code (and so all feature flag branches, mutations, conditional logic branches etc.), React components and route patterns. This suite of sessions is then used to test your pull requests.

As your app changes, and as new sessions are recorded, Meticulous will automatically update the set of selected sessions to cover the new features.

To configure the number of sessions to run, or view the current selection: visit your project page, select the 'Selected Sessions' tab, and click on 'Configure'. You generally want to select sufficient sessions such that the marginal session adds no extra coverage. Meticulous provides guidance on this in the UI.

If you're running in Meticulous cloud then test runs should generally complete in under 2 minutes.

If you wish to view your current coverage then visit your project page and click on the 'View coverage & snapshots' button. You'll be able to see the screens covered split out by route, and the sub-variants (same screen, different components visible / different states) within them. If you provide source maps then you'll be able to see coverage for each folder and file in your codebase.

We generally recommend to rely solely on automatic session selection, but if you wish you can select specific sessions to always be executed.

To do so visit your project page and click on the 'Sessions' tab. Select the session you want to add and click the 'Add to selected sessions' button in the top right hand corner. If the session is already added to the selected sessions, the button will say 'Remove from selected sessions'.