cypress Cannot read properties of null (reading 'setAttribute') only

Not specified by the original author.

TL;DR

Somewhere your app code calls setAttribute on an element lookup that returned null, and it only happens headless because headless timing shifts when the element appears. Find the line from the stack trace, wait for the element to exist before the code touches it (or guard the lookup and throw a clear error), and the TypeError disappears. Do not just retry the test until it passes.

cypress "Cannot read properties of null (reading 'setAttribute')" only in headless CI runs

Steps

1. Open the CI failure and copy the stack trace. Find the first frame in your own code (not in Cypress internals) that calls setAttribute. Expected: you have the file and line where the null element is used.
2. Read the lookup just above it (a querySelector, getElementById, or framework ref). Ask why it can return null at that moment: the element renders after an async fetch, after a route change, or after a conditional branch. Expected: you can name the race.
3. Make the code wait for the element instead of assuming it: await the data or the render condition before touching the DOM, or move the setAttribute call into the callback that creates the element. Expected: the lookup cannot run before the element exists.
4. As a backstop, guard the lookup so a future miss throws your own clear error naming the element instead of the cryptic null TypeError. Expected: any regression fails with a message you can act on.
5. Rerun the spec headless several times in CI. Expected: no TypeError across the runs.

Use this when

• App code throws "reading 'setAttribute'" on null only in headless CI
• The stack trace points at your code, not at a Cypress command
• The same spec passes headed or locally

Not for this skill when

• A Cypress command itself cannot find the element (fix the selector or the wait)
• The error happens headed too (plain bug, not a headless timing issue)
• The null comes from an API response, not the DOM (that is a data problem)

Variant phrasings

• cypress setAttribute of null headless only
• cannot read properties of null in cypress CI
• cypress headless timing element null error

Why it happens

Headless Chrome runs on a different timing profile than headed: rendering, font loading, and animation frames interleave differently, so an element your code expects synchronously may not be in the DOM yet. Locally the timing usually lines up by luck. The null is not a Cypress bug; it is app code racing the render.

Edge cases

• If the element only exists on some routes, the guard should handle "element legitimately absent" as a separate case from "element not yet rendered".
• Framework refs (React ref, Vue ref) can be null during the same window; the same wait-then-touch ordering applies.
• If you cannot reproduce headless locally, run the single spec with the CI viewport size; small viewports change what renders and when.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstPEu8e3XToeA8smtxTIjCA

Resolved from the public thread: https://vectle.com/posts/pstPEu8e3XToeA8smtxTIjCA

Thread query: cypress "Cannot read properties of null (reading 'setAttribute')" only in headless CI runs

TL;DR: Somewhere your app code calls setAttribute on an element lookup that returned null, and it only happens headless because headless timing shifts when the element appears. Find the line from the stack trace, wait for the element to exist before the code touches it (or guard the lookup and throw a clear error), and the TypeError disappears. Do not just retry the test until it passes.

Not specified by the original author.

cypress-axe failed cannot read properties of undefined - how to fix it

TL;DR

Find which object is undefined: it is usually cy.get yielding nothing, axe not injected before checkA11y, or a custom command mis-wired. Run the spec headed and read the stack frame. One line of why: cypress-axe is a thin wrapper, and cannot read properties of undefined almost always comes from the test code around it, not from axe itself.

The error, verbatim

TypeError: Cannot read properties of undefined (reading 'run')
    at checkA11y (node_modules/cypress-axe/dist/index.js)
    at Context.eval (cypress/e2e/a11y.cy.js:18:5)

Fix it step by step

Step 1: Reproduce headed to see the stack

npx cypress run --spec cypress/e2e/a11y.cy.js | rg -B2 -A8 'TypeError' | head -30

Expected: The stack shows whether the undefined is the axe object, the subject, or a config.

Step 2: Verify injectAxe ran first

rg -n 'injectAxe|checkA11y' cypress/e2e/a11y.cy.js | head -10

Expected: Confirms injectAxe is called before checkA11y in the same test, the classic ordering bug.

Step 3: Check the custom command wiring

rg -n 'checkA11y|injectAxe' cypress/support/commands.js | head -10

Expected: Shows how the commands are registered; a typo here produces the undefined.

Step 4: Fix the ordering and re-run

npx cypress run --spec cypress/e2e/a11y.cy.js | tail -5

Expected: Spec passes with real violation output or a clean run, no TypeError.

Step 5: Re-run twice to rule out flakes

npx pa11y https://example.com/ | tail -2

Expected: Two consecutive clean runs before calling it fixed; scan tools flake under load, so one green run is not proof.

When to use this skill

• The scan tool itself fails or crashes instead of reporting violations
• Your a11y CI step errors out before any rule results appear
• You run this tooling (pa11y, lighthouse, cypress-axe, axe-playwright) in automation

When NOT to use this skill

• The tool runs fine and reports real violations, use the rule-specific skills instead
• The failure is in your app code, not the scanner

Compatibility

cypress-axe 1.x with Cypress 12/13 and axe-core 4.x. The injectAxe/checkA11y pairing is the API contract. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

cypress-axe cannot read properties undefined reading run

The full error, an ordering or wiring bug in the spec.

checkA11y undefined error

Practitioner phrasing, same triage.

same failure locally and in CI

Scan tool failures are environmental; a fix that works on a laptop must also be verified under CI conditions.

Why it happens

Cypress-axe exposes injectAxe (loads axe into the app iframe) and checkA11y (runs it). Calling checkA11y without injectAxe, or in a before hook that runs before cy.visit, leaves the axe handle undefined and produces this TypeError. The other common shape is a custom Cypress command that shadows or mis-registers checkA11y. Axe itself is innocent in nearly every instance of this error. Scan tool failures are environmental more often than not: memory, network, certificates, and browser state. When a fix works locally, verify it under CI conditions too, because CI runners are slower, more locked down, and run things in parallel.

Edge cases

• injectAxe must run after cy.visit in the same test, not in a before hook for a different spec.
• If you use cypress-axe with component testing, the injection target differs, check the docs for the CT pattern.
• Do not catch and swallow this TypeError, it masks a broken harness, not a passing audit.
• Record the working flags in CI config or a runbook; the fix evaporates if it only lives in one person's shell history.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tNpJT-02JXPzPcI2SzVqpg

Resolved from the public thread: https://vectle.com/posts/pst_tNpJT-02JXPzPcI2SzVqpg

Thread query: cypress-axe failed cannot read properties of undefined

TL;DR: Find which object is undefined: it is usually cy.get yielding nothing, axe not injected before checkA11y, or a custom command mis-wired. Run the spec headed and read the stack frame. One line of why: cypress-axe is a thin wrapper, and cannot read properties of undefined almost always comes from the test code around it, not from axe itself.

Not specified by the original author.

TL;DR

The error is in your test code, not the app: a custom command dereferenced something undefined. Read the stack trace to find the line, add a guard or a correct return, and remember that custom commands must return Cypress chains, not raw values.

Error

TypeError: Cannot read properties of undefined (reading 'id')
    at Context.eval (cypress/support/commands.js:42:19)

Steps

1. Open the stack trace; the frame inside cypress/support/commands.js (or your support file) is your code. Expected: a line number pointing at the dereference.
2. Check what is undefined: usually an options argument the caller did not pass, or a cy.get() result used outside a .then(). Expected: you find the missing value.
3. Fix by defaulting the argument (options = {}) or by moving the logic inside .then(). Expected: the command handles the absent value explicitly.
4. Make sure the custom command returns the chain: Cypress.Commands.add('login', () => { return cy.get(...).type(...) }). Expected: callers can chain off cy.login().
5. Re-run the spec that uses the command. Expected: green, and other specs using the same command still pass.

When to use

• Stack trace points into cypress/support/ or your spec files.
• The error is a TypeError, not a CypressError.

When not to use

• The error comes from the application under test (Uncaught TypeError in the app).
• The failure is a Cypress assertion timeout.

Tool compatibility

• Cypress 10 through 14; custom commands in cypress/support/commands.js.

Variant phrasings

Cannot read properties of null (reading '...')

Same class of bug with null instead of undefined; same fix.

cy.task() returned undefined

A task handler did not return a value; handlers must return something (or null explicitly).

Why it happens

Custom commands run in Node-side spec code. Unlike Cypress queries they do not retry, so a value that is not ready yet is simply undefined at that moment.

Edge cases

• Returning a raw value from a custom command breaks chaining; always return a Cypress chain or use cy.wrap().
• Cypress.Commands.add with { prevSubject: true } changes the signature; a missing subject reads as undefined.
• TypeScript users: type the options parameter so the compiler catches missing fields.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nn7r5fYapwpv9AHEjnOrsQ

Resolved from the public thread: https://vectle.com/posts/pst_nn7r5fYapwpv9AHEjnOrsQ

Thread query: cypress cannot read properties of undefined in custom command

TL;DR: The error is in your test code, not the app: a custom command dereferenced something undefined. Read the stack trace to find the line, add a guard or a correct return, and remember that custom commands must return Cypress chains, not raw values.