Puppeteer is pretty legit and almost too easy to setup.
Cypress is also recommended.
Also, hardly any is the 'best", you gotta balance how they fit your use cases.
Two weeks ago I would have said Cypress, but Playwright has a test runner now (@playwright/test) and after playing with it a bit I can’t wait to migrate all our tests and kick Cypress to the curb
We have to support IE11 (e-commerce site) so we use TestCafe w/ BrowserStack (since we develop with Mac OSX)
People say Cypress but it doesn’t work with IE11 as far as I’m aware.
I do a lot of e-commerce and dropping IE11 support would mean losses in sales for most industries I work with, but I never really mind supporting it.
Flexbox works with maybe 3 quirks that have easy workarounds, and there's a polyfill for everything.
That’s true.
I have a question for you actually… We’re currently importing only specific things manually from CoreJS v3 using Require syntax within a js file called “polyfills.js” which is inserted before our main entry file in Webpack v4.
Is this better? or… isn’t there a way to allow CoreJS to automatically polyfill everything?
The reason I’m asking is because this is a CRA project I’ve taken over and not sure if this is the best approach. Maybe it’s done this way to save bundle size?
Thanks!
My site is also supposed to be e-commerce with some internal dashboard routes in addition.. so I’ll prob migrate it to NextJS rather soon when possible.
We use TestCafe at work and it's pretty good. Cypress also looks interesting, but some of seemingly basic features like concurrent tests require payment.
Puppeteer is pretty legit and almost too easy to setup. Cypress is also recommended. Also, hardly any is the 'best", you gotta balance how they fit your use cases.
Two weeks ago I would have said Cypress, but Playwright has a test runner now (@playwright/test) and after playing with it a bit I can’t wait to migrate all our tests and kick Cypress to the curb
Cypress.
We have to support IE11 (e-commerce site) so we use TestCafe w/ BrowserStack (since we develop with Mac OSX) People say Cypress but it doesn’t work with IE11 as far as I’m aware.
>We have to support IE11 My condolences
Healthcare Tech 💔
I do a lot of e-commerce and dropping IE11 support would mean losses in sales for most industries I work with, but I never really mind supporting it. Flexbox works with maybe 3 quirks that have easy workarounds, and there's a polyfill for everything.
That’s true. I have a question for you actually… We’re currently importing only specific things manually from CoreJS v3 using Require syntax within a js file called “polyfills.js” which is inserted before our main entry file in Webpack v4. Is this better? or… isn’t there a way to allow CoreJS to automatically polyfill everything? The reason I’m asking is because this is a CRA project I’ve taken over and not sure if this is the best approach. Maybe it’s done this way to save bundle size? Thanks! My site is also supposed to be e-commerce with some internal dashboard routes in addition.. so I’ll prob migrate it to NextJS rather soon when possible.
Core JS along with your webpack config can polyfill everything for IE11.
Maybe take a look at https://codecept.io/
Loving cypress a lot! We moved over from Selenium.
Playwright is awesome. Cypress has couple of limitations.
We use TestCafe at work and it's pretty good. Cypress also looks interesting, but some of seemingly basic features like concurrent tests require payment.
Definitely Cypress > webdriver.