cypress

As of yesterday Cypress binaries for older versions started blocking third-party plugins, breaking CI for multiple users. It bypasses package.lock and yarn.lock as it downloads a binary from their CDN when installing. See also: https://currents.dev/posts/v13-blocking https://www.cypress.io/blog/2023/11/07/update-defense-intell... https://github.com/cypress-io/cypress/issues/28269 https://github.com/currents-dev/cypress-cloud/issues/193

I disagree with the assertion that creating npm packages that interact with cypress is brand squatting. Names prefixed with the target ecosystem are common for discoverability and context. Trademark law prevents competitors from using another company's name and brand in a confusing way, but some reference is often needed to identify compatibility. Competition is healthy, and this feels like a much larger company taking increasingly aggressive moves towards a competitor who has created a superior hosted product in the same ecosystem. In transparency, we were using Cypress Enterprise, were frustrated with their lack of responsiveness to product suggestions and support requests and rapidly increasing costs. We switched to Currents and have been much happier with the speed, quality of product, responsiveness, and cost. We were impacted and di

I have the opposite experience. LocalStorage can leak between tests and that has been an issue for years: https://github.com/cypress-io/cypress/issues/2695

It sure does. The way Cypress works is that it injects their entire driver (test API) to the browser and then loads the tests themselves, also in the browser. It is a finicky process because they need to rewrite all JS and HTML (https://github.com/cypress-io/cypress/tree/develop/packages/...). It is slow because they have to proxy everything through HTTP 1.1 proxy (https://github.com/cypress-io/cypress/tree/develop/packages/...). The thing that I built takes a different approach. It parses Cypress tests, interprets the commands that Cypress wants to run, and then uses Chrome DevTool protocol (CDP) to evaluate commands such as navigation, click, etc. If you are familiar with the JavaScript ecosystem, my tool effectively transforms tests to Playwright compatible tests and then uses custom orchestration logic to run them.

There are probably newer tools for this, but we use `eslint-plugin-expect-type` [0] for this: https://github.com/cypress-io/cypress/blob/develop/cli/types... [0]: https://github.com/JoshuaKGoldberg/eslint-plugin-expect-type

We wrote E2E tests with Cypress before Playwright was around and it was awful. The API is weird to the extent that it is basically a DSL based on Javascript. And the tests were flaky because rerenderings could happen between Cypress getting the DOM element and interacting with it. It seems they haven't fixed that one to this day.[0] The team is also very confident about their approach. They build their own asynchronous concepts that are not interoperable with async/await, openly acknowledge that it is hard to wrap your head around and then dismiss these concerns by asserting that "Asynchronous APIs are here to stay in JavaScript.".[1] The Github issue about the lost DOM elements is also full of answers by a team member intent on writing blog posts that explain what the user is doing wrong rather than fixing the root problem. I'm really gl

> such as multi-domains aren't supported Thankfully this is being actively worked on: https://github.com/cypress-io/cypress/issues/944#issuecommen...

Top-scored projects: https://commondatastorage.googleapis.com/ossf-criticality-sc... For JS: node│https://github.com/nodejs/node│JavaScript│73│0│3226│10│64.7│63│1517│2055│4.1│10499… react-native│https://github.com/facebook/react-native│JavaScript│71│0│2866│5│50.5│15│778│1694│3… react│https://github.com/facebook/react│JavaScript│91│0│1609│6│20.9│6│692│973│3.8│333619… gatsby│https://github.com/gatsbyjs/gatsby│JavaScript│67│0│3873│3│83.3│2│2181│2526│1.9│118… three.js│https://github.com/mrdoob/three.js│JavaScript│130│0│1694│8│64.3│12│606│801│3.1│229… bootstrap│https://github.com/twbs/bootstrap│JavaScript│113│0│1360│7│21.7│9│729│912│2.1│14966… material-ui│https://github.com/mui-org/material-ui│JavaScript│76│0│2256│7│53.8│43│1561│1826│2.… odo

The flag --disable-background-networking might break some sites: https://github.com/cypress-io/cypress/issues/1320

I use Cypress with this plugin: https://github.com/palmerhq/cypress-image-snapshot In my setup, it creates the PNG snapshots and compares them to the snapshots stored in Git at each test run. In result, I get the number of different pixels and the test fails if the nunmber is higher than 0. It also produces a visual PNG diff file, that has 3 panes: expected, actual, diff heatmap. The setup took just few hours. However there are some screen resolution limitations in Cypress right now. I could not get it to work in resolution higher than 1200x1024. More about that problem: https://github.com/cypress-io/cypress/issues/2102

How do you learn to read code without guidance and without getting lost? How do you keep your thoughts organized? At each step, how do you confidently decide where to go next? ——— I’d like you to take as given that I’m reasonably intelligent — I graduated from MIT and have been working as a software engineer for 6 years. Yet when I sit down to read https://github.com/cypress-io/cypress or https://github.com/webpack/webpack, I don’t know where to start or how to incrementally build up an understanding. How can I learn how to read a project’s worth of code?

- Docs: https://docs.cypress.io - GitHub: https://github.com/cypress-io/cypress - Gitter: https://gitter.im/cypress-io/cypress