Cypress Studio AI chooses selectors using a configurable priority order, then uses observed changes in the page’s DOM to suggest assertions. Before sending data to its AI model, Cypress excludes values from documented password, credit-card, and hidden input fields—but this is not a blanket promise to redact every sensitive value in an application.
How does Cypress Studio generate selectors?
Studio automatically selects a unique locator for elements you interact with, assertion targets, and AI recommendations. Cypress describes its goals as uniqueness, readability, and performance. The documented default preference order is:
As an Amazon Associate I earn from qualifying purchases.
data-cydata-testdata-testiddata-qanameidclass- tag
- other attributes
nth-child
This is a preference order, not a guarantee that Cypress will use the first available attribute. If a candidate does not identify the target uniquely, Cypress may skip it or combine selectors. Selector behavior is under active development, so check the documentation for the Cypress version your project uses: Cypress Studio AI and Element Selector API.
Recommended Free Tools
Can I change which selectors Cypress Studio prefers?
Yes. Configure selectorPriority with Cypress.ElementSelector.defaults(). For example, this project-specific order prioritizes semantic and accessible attributes before test-specific attributes:
Cypress.ElementSelector.defaults({
selectorPriority: [
'role',
'aria-label',
'data-cy',
'data-test',
'data-testid',
'data-qa',
'name',
'id',
'class',
'tag',
'attributes',
'nth-child'
]
});Use attributes that are meaningful and stable in your application. A dynamic ID or generated class can change between builds; an accessible role or label may better reflect user-facing behavior. Still inspect generated selectors: uniqueness at recording time does not guarantee the markup will remain stable as the application changes. Cypress labels this configuration API as under active development.
How does Studio AI decide what assertions to suggest?
Studio AI observes DOM changes between recorded interactions and proposes assertions that reflect visible UI changes. It does not inspect your application source code, business logic, or backend rules. Treat a suggestion as a starting point: confirm that the assertion checks the intended behavior and that it is reliable across relevant test states.
Studio recording and manually adding assertions work without Cypress Cloud. AI recommendations require a Cypress Cloud account and a linked project. The Studio AI guide lists Cypress 15.11.0 or later as a requirement. It is intended for end-to-end testing; the guide lists component testing, Cucumber-style tests, multi-origin recording, iFrames, and Shadow DOM as unsupported. It also notes that animations or transitions can produce intermediate DOM differences, large pages may exceed context limits, and Studio AI does not crawl an application automatically. These product requirements and limitations can change; verify them against the current guide.
Does Cypress Studio AI send passwords or credit card values to the AI model?
Cypress documents exclusions for values in password inputs, hidden inputs, and credit-card fields identified using standard autocomplete attributes, including card name, number, expiry, security code, and card type. Cypress says those values are excluded before data is sent to its AI model. The fields’ structure and surrounding context can still be used to generate assertions; only the values are excluded. These are statements in Cypress product documentation, not an independent security assessment.
Does Cypress Studio redact all sensitive data?
No blanket redaction guarantee is established by the documented field exclusions. They cover the specified input types and credit-card autocomplete cases—not arbitrary visible personal information, custom fields, or every secret-bearing part of application state. Review what is visible in the page and avoid assuming that unlisted values are automatically removed.
Take extra care with cy.prompt
A secret written literally in a natural-language cy.prompt step is part of that prompt; the DOM-field exclusions do not protect it. Cypress recommends passing sensitive information through placeholders and says placeholder values are never sent to the AI model. Follow the current guidance for cy.prompt when handling secrets.
Rank #4
What controls are available for Studio AI?
A user can disable Studio AI for an individual session. Cypress also documents organization-level controls in Cloud settings that admins or owners can use to disable AI capabilities. Consult the Studio AI guide for the current controls and their locations.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Or skip the browser setup:
If your goal is to capture a page rather than record a Cypress test, ScreenshotNeo offers a one-request screenshot API. For example, this cURL request saves a WebP capture of Stripe; create an API key and replace YOUR_API_KEY before running it. See the ScreenshotNeo API documentation for request options.
Best Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp- Cookie banners and consent notices, newsletter popups, and chat widgets are handled before capture; each cleanup step can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Response headers report the page verdict and billing status.
- An MCP server provides screenshot and PDF tools for AI agents, including Claude, Cursor, and other MCP clients.
- The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Frequently Asked Questions
Can I use Cypress Studio without Cypress Cloud?
Studio recording and manual assertions work without Cloud; AI recommendations require a Cypress Cloud account and linked project.
Does Studio AI read my application’s source code?
No. Cypress says Studio AI bases recommendations on observed DOM changes, not application source code, business logic, or backend rules.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
