--- title: "cy.blog()" url: "https://www.cypress.io/blog/page/50" description: "Page 50: Releases, AI-assisted testing, and quality guides from the Cypress team. See what changed, whether it affects you, and how teams ship with confidence." --- # cy.blog() Releases, AI-assisted testing, and quality guides from the Cypress team. See what changed, whether it affects you, and how teams ship with confidence. [Meet cypress tap: give your AI agent the context the Cypress app shows you Cypress AIcypress tap is a new set of CLI command to pull Cypress app context into your terminal. It lets AI agent drive a Cypress open session from the terminal, so it can author new tests, extend existing ones, and read failures the way the Cypress app shows them.Read more](/blog/cypress-tap-cli) [All](/blog)[Releases](/blog/category/Releases) [Community](/blog/category/Community) [Education](/blog/category/Education) [Customer Stories]() [Company](/blog/category/Company) [Cypress is now public beta The first commit on Cypress happened on June 5th, 2014 - exactly 3 years, 4 months, and 5 days ago. Since then we have had 20,000+ commits across all of our projects, we have created 100+ repos, and received 10,000+ early adopter submissions. We’ve funded Cypress by raising money, and with that built a solid team of some of brightest talent in JavaScript. Cypress has come a long way since the early days. We’ve overcome seemingly insurmountable technical challenges. We’ve solved some of the har Read more](/blog/cypress-is-now-public-beta) [Good error messages If I can paraphrase a cliché: bad things happen to good programs Things go wrong, even in the most carefully coded and thoroughly tested applications. In my opinion, a sign of a good app is if it gives meaningful and useful error messages when things go wrong. At Cypress we spend a lot of time trying to make every type of error we display to the user as useful as possible. These include failed assertions during tests (after all, Cypress is an end to end test runner), and crashes insid Read more](/blog/good-error-messages) [10 ways we improved our docs As part of our strategy towards going open source, we wanted to make several improvements to our documentation. There were a few problems we wanted to address: 1. There was no clear explanation of why you would want to use Cypress. 2. There were no clear “Getting Started” guides that introduced you to Cypress. 3. Most API commands were missing explanations of critical core concepts. 4. We found many users were confused by the Cypress ✨ magic ✨. 5. Our users asked the same questions o Read more](/blog/10-ways-we-improved-our-docs) [Immutable deploys and Cypress It is simple to run Cypress both locally and on CI. And it is simple to point your tests to a different server. If you are using immutable deploys, Cypress can be the ultimate “health check”. If the tests pass locally, then on CI, and then at a newly deployed environment - the chances are very high that you can point production DNS record at the new deployment and it will work. Here is an example. Let us take a “stock” React TodoMVC app \[https://gitlab.com/bahmutov/todomvc\] and see all the mome Read more](/blog/cypress-and-immutable-deploys) [Why I joined the Cypress.io team You know what is hard? Changing jobs is hard. Testing web applications is hard. Luckily for me, I have an opportunity to tackle both problems at once! I am happy to announce that I am joining the awesome Cypress.io \[https://www.cypress.io/\] team. This is a big personal change. I spent last three years developing web applications for financial startup, Kensho. I was happy to see Kensho grow from 10 people to 75 and sign very first contracts. > I want the software to be better and by extension m Read more](/blog/why-i-joined-the-cypress-team) [Atom test utils At Cypress, we love creating tools that make testing easier and more productive. We also write a lot of tests ourselves to both guide our development and help prevent regressions. While having a lot of tests is a great way to prevent regressions, it can get in the way of getting quick feedback during development. The more tests there are, the longer it takes to run them all, which can slow things down. Fortunately, we can have it both ways. We can focus on certain tests during development, but Read more](/blog/atom-test-utils) [Cypress is going open source! That’s right! After years of development and focused iteration with our early adopters, the most advanced front-end testing tool in the universe is almost ready for its ultimate adventure: going open source! Here at Cypress HQ, we generally have several projects in motion at a time and this open source initiative is no exception. Let’s look at a few of the things that are coming down the pike for this launch. Documentation overhaul Over the last couple of years, our documentation has grown l Read more](/blog/cypress-is-going-open-source) [Newer posts](/blog/page/49)