Back in September 2020, our own Eric Wagoner wrote about his first experience with Cypress, touching on its ease of setup, easy to read and write syntax for JavaScript developers, and some of the team-related benefits of incorporating Cypress testing into a project. Since then, we’ve continued to work with several clients using Cypress - whether building out a testing infrastructure from scratch or helping them expand their tests and testing capability. We’ve learned a lot over the past few years working with Cypress and in this post, I’ll share some of the biggest benefits we noticed both from a QA and development perspective.
…read more
We recently were a part of a project with what was, in many ways, a
typical successful startup. The company makes hardware for a niche
market, powered by their own firmware and driven by a suite of web
applications running both on a server and locally as
Electron apps. They make a great
product that is disrupting the space and they’re growing rapidly, both
in company size and number of users.
What started as a small integrated team has spun up to several groups
overseeing various aspects of the product and as that happened the
developers became somewhat siloed from the QA folks. Each group had
its own process for keeping the quality high in the face of rapid
growth, namely thorough unit tests on the development side and a
series of step-by-step documents used by a number of testers to
manually go through every page and every button of the web
applications. Releases were coming quickly and the testers were
spending hours upon hours methodically testing only to have to start
all over again when another release came out of development. They were
overworked and almost overwhelmed, and called Infinity for help.
…read more
