re: Cypress vs..... VIEW POST

FULL DISCUSSION
 

I used Cypress on a project and loved it, but I have a hard time selling it to stakeholders because it isn't cross browser.

Chrome is rarely the browser with weird bugs so testing there is considered happy path. :/

 

Chrome is rarely the browser with weird bugs so testing there is considered happy path. :/

So true, since most developers use Chrome as their main dev and debugging browser - of course it looks perfect - it's a classic "it works on my machine", except replace "machine" with "browser".

I'm pretty guilty of this tendency as well. I hope to see Firefox and Edge catch up to offer a better experience for developers.

 

I tried to switch to FF twice this year, but while the dev tools is great, performance is noticably slower compared to Chrome on many websites.

Also, ReCaptcha is so nasty on non-Chrome browsers, I spent 5 minutes solving a challenge and still I was getting more puzzles (it's not FF's fault, Google's ReCaptcha is just so fucked up).

ReCaptcha is so nasty on non-Chrome browsers, I spent 5 minutes solving a challenge and still I was getting more puzzles

That is a privacy price I'm willing to pay.

I can't comment on performance. I have been using Firefox since 0.4. I only use chrome when needed to verify non-standard webstuff. Firefox never felt slow to me.

Haha yeah... I'm spoiled by Chrome now - but these days either Chrome is slowing down or websites are getting fatter... - I might jump in to migrate to FF again.

 

Precisely, if I have to test manually on all supported browsers, it would be counterproductive.

Off topic, but I like Firefox Devtools and they're adding some nice new features like letting you know when css props is not having any effect, but I am very used to the Chrome experience so hard to change. :P

code of conduct - report abuse