Cypress.io

When testing is easy, developers build better things faster and with confidence.

Join 25k testing professionals at CypressConf 2026: 🚀

[Cypress.io @Cypress_io]

Passing tests don't always mean confident deployments. 🫠

#CypressConf26 is where testing teams will explore what makes the difference – October 20-22, virtual and free.

Register:
https://t.co/lpZlUolQBc

[Cypress.io @Cypress_io]

Boris Selivanov treats being a Cypress Ambassador as high-impact over high-volume. The same standard he holds his tests to: build it so it holds up, not just so it works today.

Full spotlight on Boris → https://t.co/T16B3eP3lG

[Cypress.io @Cypress_io]

Your AI agent can now read the same failure context you do.

Cypress Cloud CLI is live, giving your agent deep access to Test Replay: commands, network activity, and failure context.

Hand your agent a failed run and let it work. Details 👉 https://t.co/FGaLXIbUPT

[Cypress.io @Cypress_io]

A green Cypress run feels like confidence. Is it always telling the truth?

Mairaj Hydary is challenging the assumption that passing tests automatically equal product quality, at #CypressConf26.

Reserve your seat today: https://t.co/LkSLnJFerq

[Cypress.io @Cypress_io]

Running Cypress through an AI agent? The test output rides in context long after the run, re-read on every turn.

The fix is two simple CLI flags Cypress already has. Set once, applied everywhere. Full stack traces stay.

How: https://t.co/no4z2dYkma

[Cypress.io @Cypress_io]

@yashpreetOnX We'll have more to share on the App CLI soon!

[Cypress.io @Cypress_io]

Meet Javier Flores, QA Automation Lead and Cypress Ambassador, and educator.

His approach? build confidence through real reps which is how he approaches everything from mentoring his own team to community education.

Read our newest spotlight → https://t.co/R6ZLsHKDjl

[Cypress.io @Cypress_io]

Cypress Accessibility runs automated checks on every test. In a shared app: QA, dev, and product each read that differently each with their own responsibilities and definitions of "done."

Watch "Solving Cross-Team Accessibility Challenges with Cypress": https://t.co/sUFlkjmmhD

[Cypress.io @Cypress_io]

Cypress now installs with Bun.

bun add --dev cypress (Bun v1.2.22+)

CI restoring from a lockfile? Bun skips postinstall, pull the binary yourself:
bun install --ignore-scripts && bunx cypress install

Details: https://t.co/scKypcnUAJ

[Cypress.io @Cypress_io]

Tatiana Mikhaleva, Founder of https://t.co/nqoXnUdF9Z, believes reliable automation isn't about gatekeeping, it's about giving engineers confidence (and their weekends back).

Meet our latest Cypress Ambassador: https://t.co/oUPEOHzr9x

[Cypress.io @Cypress_io]

AI that fixes your tests shouldn't hide what changed.

When a selector breaks, cy.prompt() regenerates the step so the run continues, and badges it in the Command Log locally in Test Replay for CI.

Every heal shows the old selector, the new one, and how.

https://t.co/SX8hOgappr

[Cypress.io @Cypress_io]

UI Coverage knows what your tests miss. Now your AI agent can too.

With Cypress Cloud MCP, your agent can pull coverage, find what's untested on a page, and draft tests that close the gap. You review and decide what ships.

Walkthrough 👉 https://t.co/Jp1rv7ZNIP

[Cypress.io @Cypress_io]

Flaky tests are inevitable, what happens next is a choice. Left unaddressed, they erode the one signal that matters: are we safe to ship?

At #CypressConf26, Josué Lobo, built an automated triage system on Cypress Cloud to fix that.

https://t.co/mtgAFuCSql

[Cypress.io @Cypress_io]

Passes in Electron, fails in Chrome? That gap is Electron sitting between your tests and the browsers your users run.

Cypress v16 closes it by moving off the bundled Electron browser to installed ones.

Get ahead of the migration today: https://t.co/ds66i3ro1a

[Cypress.io @Cypress_io]

LLMs don't give the same answer twice. So how do you write a test assertion against one?

At #CypressConf26, Anvesh Puli, talks building a "trust layer" for AI products with Cypress that allows you to ship with confidence.

https://t.co/cVk3gvvtlY

[Cypress.io @Cypress_io]

The Cypress migration guide now has ready-made upgrade prompts.

Open the guide, copy the prompt from your version's section into your AI coding assistant, and review each change it makes.

Prompts:
https://t.co/mRCjjgy6Ij

[Cypress.io @Cypress_io]

When an AI coding agent runs Cypress, the test output doesn't go away when the run ends. It sits in context and re-read every turn for the rest of the session.

We call it the context passenger. We measured what it costs and cut Cypress run bloat 75%.

https://t.co/no4z2dYkma

[Cypress.io @Cypress_io]

DYK: cy.prompt can now wait for network requests ✅

Reference an alias name directly inside your prompt instructions, and Cypress will handle the wait – without requiring you to exit the flow.

Check it out: https://t.co/8CJow7eSnA

[Cypress.io @Cypress_io]

Every test suite has its enemies: flakiness, brittle coupling, tests that collapse when the product shifts.

At #CypressConf26, Gilberto Mares shares an architecture for atomic testing in Cypress that tackles them head on.

Register today: https://t.co/2xnv7YjOQH

[Cypress.io @Cypress_io]

The best part of a barbecue isn't the food, it's the people who show up. 🍖

Same goes for the Cypress Discord. It's where devs gather to talk shop, trade fixes, and figure out that one flaky test together.

Pull up a chair while the grill cools off. 👇
https://t.co/NUGqnQRY1K

[Cypress.io @Cypress_io]

Spotlighting Cypress Ambassador Anvesh Puli.

He's driven by the "build and break" cycle, pushing testing tools until he finds where they crack. That mindset earned him an IBM Tech award and fuels his knack for untangling "unsolvable" issues.

Read more: https://t.co/gE0WhsfnTs