Home / Companies / Cypress / Blog / Post Details
Content Deep Dive

New: Finish Cypress Cloud runs faster with the Run Completion API

Blog post from Cypress

Post Details
Company
Date Published
Author
-
Word Count
783
Company Posts That Month
7
Language
English
Hacker News Points
-
Post removed?
No
Summary

Cypress Cloud has introduced the Run Completion API for all plans, enabling teams to finalize test runs immediately once recording ends rather than waiting through the configured Run Completion Delay for additional test groups. Cypress Cloud commonly consolidates groups running across different machines, browsers, test types, operating systems, and environments into one run, supporting unified results, failure triage, accessibility reporting, and UI Coverage metrics. While the existing delay, which defaults to 60 seconds, helps accommodate staggered CI jobs without affecting CI idle time, a long delay can postpone terminal pass/fail status, reports, notifications, and integrations. The new API preserves the flexibility of a longer buffer while allowing teams to explicitly close a run when all expected tests are complete, improving the speed of post-run workflows such as accessibility and coverage reports, Slack or Teams alerts, desktop notifications, and CLI or MCP data access. It can be called through Cypress’s after:run configuration hook with an expected group count or invoked after required CI jobs finish without specifying a count.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
MCP 1 8,729 854 211 -20%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.