Better world by better software

Recently I saw a Linkedin post that shows "before & after" API test using Cypress.

Let's say you have a long-ish Cypress test and you know a place where it might fail.

Imagine a typical application that loads some data.

Have you ever encountered end-to-end test error "... failed because the page updated as a result of this command, but you tried to continue the command chain.

Let me get back to the testing of negative states one more time.

Imagine a simple web application scenario: you click on a button.

Cypress-the-company is putting a lot of effort behind its cy.prompt command (which I recreated in cypress-think), so let's see if it is any good.

Finally, it has happened.

I have a little web app called Gametime I use to keep track of players during youth soccer matches.

Every individual item sold on Mercari.com has an id that looks like m<number>.

Recently Cypress announced a change in how it will handle environment variables.

Cypress v15.10.0 has announced a big switch coming in v16 - the new way of dealing with environment values and secrets.

At the end of 2025, NPM registry revoked all personal NPM tokens that I used to publish new NPM package releases.

Imagine you are testing a TodoMVC application, and you need to complete all items.

If you are testing a website, the DEV dependencies do not change very often.

This year I am reclaiming my attention span away from my iPhone.

Here is something I have noticed about my projects and using Copilot lately.

Loading skeletons are displayed while the real data is loading.

In Cypress you can save values under aliases which is pretty handy.

Well, I am happy to report Cypress-the-company is all in on test auto-healing in its new cy.prompt command (which I recreated locally as cypress-think plugin).

Let's say you need to specify a timeout or wait in your end-to-end Cypress tests.

This year I am producing "Cypress vs Playwright Advent Calendar" on my Cypress Tips newsletter.

Imagine we are testing a web page that receives two numbers from the server and then shows their sum In the Command Log you can see the two GET /random-digit calls the web page makes to the server.

I have described using Use Copilot Instructions And Page Objects to quickly develop end-to-end Cypress tests.

Imagine you are testing a web page showing the purchase receipt.

Recently I watched a pretty good video Cypress vs Playwright side-by-side coding comparison. by Artem Bondar.

Testers and developers often use page objects to interact with their web applications via DOM elements.

As I explained in my previous blog post on feature flags and testing, you need the flags to be the same to ensure consistent application behavior during end-to-end tests.

I have shown how to use Copilot instructions file to generate better end-to-end Cypress tests.

If your web application stores data locally in the localStorage object, you can easily set / verify the data from your Cypress end-to-end tests.