An approach that many teams follow, is to spend a lot of time getting someone from the QA team to manually regression testing a website before any change is pushed live. I believe that most companies aim to have fully automated test coverage, however, from my experience, very few companies have invested the time and effort required to have coverage that they feel confident pushing code into production without anyone needing to manually check some stuff.
What Is Cypress?
No one in the DEV or QA team moaned about using Cypress
More functional tests were written by developers
As tests are co-located near the component like unit tests, they became more useful for developers as a tool to understand what the code does better.
QA can easily learn CVypress given some help and coaching
Simplified Git and CI/CD set-up. Not having a separated Java test project allowed for better standardisation
You can get a demo Cypress project up and running within 15 minutes, so there really is no excuse not to give it a try. You can download Cypress from NPM and there is good documentation of how to get set-up over at the Cyprus website here. Over the years, when I've worked on projects and introduced new technologies, there's always a certain amount of pushback. As is human nature, some people tend to resist changing things. As of yet, I haven't heard one person complaining about Cypress, so that in itself says a lot about the product, best of all... it's FREE! I recommend you start using Cypress today, you will not regret it. Happy Coding 🤘