What can you see while you write a Cypress test?

In interactive mode, Cypress shows your app and a log of the steps it ran. Open a command in the log to see where a test started behaving differently from what you expected.

Studio can record your actions into a test file. After choosing a time and clicking Book, add an explicit check for the result. Try a single path while you get used to the runner. A useful first one is a booking you can find again after refreshing the page.

Manual Studio needs an internet connection and source maps, which connect what runs in the browser to the project files you edit. You can use manual recording without a Cypress Cloud account. Automatic suggestions are an optional Studio AI feature. Continued use requires a Cloud account and a linked project.

How do you record a booking test you can trust?

Start from a fake customer and a predictable slot. Record the clicks, add an expected result and make sure Cypress reports when it is missing.

Confirm where the app will save
Use a separate test database and sign-in settings. Use fake details. Keep payments and reminders off or connected only to test services you control.
Record and add a check
Start Studio in the test project. Reserve the slot, reopen the booking list and add a check for the saved time. Review what Studio put in the test file. Studio cannot record steps across different sites. If sign-in opens a separate site, verify sign-in on its own and start your booking test with a signed-in test account.
Make the runs independent
Give the available-slot and taken-slot cases their own starting records. Clearing browser state does not clear the appointments the app already saved. If the account’s booking should follow the customer to a new browser, check that separately with a fresh browser session.
Try the failure on purpose
On the test copy, make a fake booking appear to succeed without saving it. The check should fail when you reopen the list. Restore the normal behavior and run it again.

Which browsers and failure records can you use?

The Cypress App supports Chrome-family browsers and Firefox, with experimental WebKit support. Use the local command log while editing. Use the artifacts from the actual run when a shared test fails.

Where to look when a Cypress check fails
Where you ran it	What you can inspect
Interactive Cypress App	Step through the command log and look at page snapshots around the failing action.
Automatic run	Check the runner output and configured screenshots or videos. The app captures failure screenshots by default in run mode.
A supported Chromium run recorded to Cypress Cloud	Test Replay can show recorded page changes, requests and console activity. Check browser support before relying on Replay for a run.

When does Cypress Cloud count a result?

The open-source Cypress App has no subscription fee. If you record runs to Cypress Cloud, its free Starter plan lists 500 recorded test results per month, up to 10 users and 30 days of retention.

The limit counts the individual tests that executed and were recorded. If you run and record all 20 tests, that uses 20 results. Retries of the same test are counted once, and skipped or unrecorded tests do not count.

If your plan has no on-demand usage and you pass its limit, Cypress says recording continues, but new results are hidden and Cloud parallelization is disabled until the allowance resets or you upgrade. Estimate the count across the browsers and automatic runs you actually plan to use.

What stays in your project, and what can Cypress receive?

The test files stay with your app. Recording to Cypress Cloud can send test definitions, output, screenshots and other artifacts. Test Replay can also include page content and requests.

Studio AI is separate from recording a run to Cypress Cloud. If you opt in, including during the trial without an account, it can send information from the page to suggest checks. Decline the trial or turn off suggestions in the Studio panel if you only want to record manually.

Use fake data even for a private project and check the capture settings before sharing a run. A recording of a test account can still include information you did not intend to share. Keep the test files and any essential, permitted evidence in storage your team controls.