3 ms·
Recently, we hat to add some front-end tests for the admin panel of the product. QA jointly with front-end team decided to use Cypress. I think, front-end were
by crabbone 3y ago
Recently, we hat to add some front-end tests for the admin panel of the product. QA jointly with front-end team decided to use Cypress. I think, front-end were already using it for unit tests (aptly named by Cypress end-to-end tests), and QA decided to piggy-back on that...
I was involved with some automation process where I also had to touch the contents of these tests. Dear lord... I never liked Selenium, but this thing... it's so hilariously bad. Well, maybe I've not touched anything front-end related for a while, so I'm getting out of touch with the depth of stupidity modern Web development plunged into.
But... if this decision (of blocking someone) adversely affects Cypress and helps them disappear, I will only be happier. This is just an insanely bad product with insanely bad ideas. I struggle to comprehend how something like this gets so much attention and so much work put into it.
- phatskat 3y agoSo I’ve been using Cypress on and off for a while at different jobs, and recently pushed for it for our front end E2E suite. Personally, it’s always been a breeze to use and rather straightforward. It took me a day to mock logins in our relatively complex login system, and not even half a day to get a suite of backend interceptors written to mock our GraphQL backend for when we need to run tests without access to the backend. Test suites are fairly quick to write up, and there’s nothing overly complex or “weird” I’ve had to do with the syntax. This is all coming from a biased perspective for sure - I’d love to hear some specifics about what gave you this kind of reaction to Cypress.