testcafe

I found testcafe (https://github.com/DevExpress/testcafe/) also very enjoyable. Long live E2E tests!

So far in the wild I've mostly seen it being used to confuse. Like in the very first part of the TestCafe documentaion (https://github.com/DevExpress/testcafe#creating-the-test): fixture `Getting Started`// declare the fixture .page `https://devexpress.github.io/testcafe/example`; // specify the start page //then create a test and place your code there test('My first test', async t => { await t .typeText('#developer-name', 'John Smith') .click('#submit-button') // ... }); I spent ages going through their docs trying to find out why they specify their two main functions differently (`fixture` using tagged templates and `test` as a regular functions). In the docs it mentions "doesn't matter which way you do it". It's just there to confuse / impress.

Indeed, I see lately many cool projects emerging. Is a pity that not all projects are using the same GitHub tag #headless-chromium [1] This other project[2] was recently on HN but you can't find it easily on github search. [1] https://github.com/search?q=topic%3Aheadless-chromium&type=R... [2] https://github.com/DevExpress/testcafe

You're completely right! It's unfortunate but the tooling for e2e tests isn't "there" yet. For now the best alternative is Selenium (which I've had a lot of trouble with getting stable) or https://github.com/DevExpress/testcafe

I tried to set up a system like this for catching differences between browsers but eventually gave up. I used selenium which didn't work well at all as the browsers constantly lost connection ur hung. I think testcafe [1] looks like a promising alternative. Image diffing is the simplest part but getting consistent images to compare can be tricky. Automatically finding regressions with few false positives ain't easy. [1]: https://github.com/DevExpress/testcafe