NEWHow to check your Claude Code token spend  →
← Back to blog
Cypress, GitHub Actions, and Shipyard for E2E testing

E2E Testing With Cypress, GitHub Actions, and Shipyard

Check out our webinar with Cypress' Ely Lucas and learn how to shift E2E testing left in your CI/CD pipeline with Cypress, GitHub Actions, and Shipyard.

We spoke with Cypress’ Ely Lucas about the virtues of unblocking your CI/CD pipeline with instantly-available ephemeral environments. When you have a robust automated testing suite, the only thing holding you back from a faster feedback loop is testing environment availability. Your team has devoted valuable time developing thorough, comprehensive E2E tests, why not run them sooner and more frequently?

In this webinar, we demonstrate how you can set up your CI/CD pipeline to run Cypress E2E tests directly against your Shipyard ephemeral environments. This empowers you to test before merging — you can shift left by fixing things before they break your staging. Check it out below and learn how to use these tools in tandem to get the most out of your CI/CD provider.

Community

Chat with the Shipyard community on Slack.

Trade tips with other devs and DevOps teams, get help from our crew, and hear about events before they go live.

Join Slack →
Latest from the blog
Claude Code CLI cheatsheet with commands, configuration, and best practices

Claude Code CLI Cheatsheet: config, commands, prompts, + best practices

Get leet @ Anthropic's Claude Code with this cheatsheet, including config, CLI commands, advanced features, and best practices for faster dev + test.

Read the article →
Newsletter

Stay in the (inner) loop.

Hear about the latest and greatest in cloud native, agents, engineering, and more when you sign up for our monthly newsletter.