Testing New Added 8 September 2026

Cypress: Cypress detected a cross origin error

The test navigated to a different origin. Cypress runs in the same browser context as the application, so it can only automate one superdomain at a time unless the visit is wrapped in cy.origin, which is what breaks tests that go through a hosted login page.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

// Wrap the other origin explicitly
cy.visit('https://app.example.com');
cy.contains('Log in').click();
cy.origin('https://auth.example.com', () => {
  cy.get('#username').type('user');
  cy.get('#password').type('pass');
  cy.get('button[type=submit]').click();
});

// Variables must be passed in: the callback is a separate context
cy.origin('https://auth.example.com', { args: { user } }, ({ user }) => { ... });

// Better: skip the UI login altogether
cy.session('user', () => cy.request('POST', '/api/login', creds));

How to diagnose Testing errors

Test errors divide into infrastructure problems (the framework cannot find or load your tests, fixtures or modules) and flakiness, which is the more expensive category. End-to-end timeouts are almost always a race between the test and the application, and the durable fix is to wait for a condition (an element, a network response, a state change) rather than for a duration.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Run a single failing test in isolation. If it passes alone but fails in the suite, you have shared state or test ordering dependence.
For Cypress and Playwright timeouts, use the trace viewer or video to see what the page actually showed. The element usually exists but is covered, detached, or not yet interactive.
Replace fixed waits with condition-based waits. waitForSelector and auto-retrying assertions eliminate an entire class of flakiness.
For collection and module-resolution errors, check the framework's rootDir/testPaths configuration and the presence of __init__.py or conftest.py where the framework expects it.
Review snapshot diffs rather than updating them reflexively. A changed snapshot is sometimes a real regression.

Tools worth reaching for

playwright show-trace
pytest -x -vv --tb=long
jest --runInBand
cypress open
test retry analytics

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

docs.cypress.io

Related Testing errors

See all 18 Testing errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.