I recommend using https://devexpress.github.io/testcafe.
Pros:
•	easy install
•	complete test harness
•	javascript ES2016 with (async/await)
•	flexible selector system
•	smart assertions with a retry policy
•	reports
See the simple tutorial here.
https://codecept.io/testcafe/#cons


So far, TestCafe is the only framework that provides native testing experience for Vue.js applications. Let’s see how easy it is to test a Vue.js application with TestCafe.

Español, ejemplo muy simple https://www.paradigmadigital.com/dev/testcafe-el-aliado-perfecto-para-el-desarrollo-de-tus-tests-e2e/

https://medium.com/technical-credit/end-to-end-testing-for-react-vue-etc-18b85e10c6f0


https://medium.com/clockwork-nl/mastering-testing-with-vue-js-by-testing-a-real-application-and-setting-up-ci-cd-e4e989c12912


https://dev.to/heyshadowsmith/vue-component-tdd-with-jest-and-storybook-52od




https://codecept.io/testcafe/#cons

Pros
•	Fast. Browser is controlled from inside a web page. This makes test run inside a browser as fast as your browser can render page with no extra network requests.
•	Simple Cross-Browser Support. Because TestCafe only launches browsers, it can automate browser on desktop or mobile. Unlike WebDriver, you don't need special version of browser and driver to prepare to run tests. Setup simplified. All you need is just a browser installed, and you are ready to go.
•	Stable to Execution. Because a test is executed inside a browser, the network latency effects are reduced. Unlike WebDriver you won't hit stale element exceptions, or element not interactable exceptions, as from within a web browser all DOM elements are accessible.
#Cons
•	Magic. Browsers executed in TestCafe are not aware that they run in test mode. So at some edges automation control can be broken. It's also quite hard to debug possible issues, as you don't know how actually a web page is parsed to inject automation scripts.
•	No Browser Control. Because TestCafe do not control browser, you can't actually automate all users actions. For instance, TestCafe can't open new tabs or open a new browser window in incognito mode. There can be also some issues running tests on 3rd party servers or inside iframes.
•	Simulated Events. Events like click or doubleClick are simulated by JavaScript internally. Inside WebDriver or Puppeteer, where those events are dispatched by a browser, called native events. Native events are closer to real user experience. So in some cases simulated events wouldn't represent actual user experience, which can lead to false positive results. For instance, a button which can't be physically clicked by a user, would be clickable inside TestCafe.
https://medium.com/yld-blog/evaluating-cypress-and-testcafe-for-end-to-end-testing-fcd0303d2103

https://dzone.com/articles/selenium-can-it-compete-with-cypress-and-testcafe

In the Red corner: TestCafe
TestCafe definitely has some valuable features that I’m very much interested in. Here are my top four favorite TestCafe features.
1.	Browser handling: It can run tests simultaneously in any browser, and no, it doesn’t need any complex configuration (including mobile devices and cloud services).
2.	Headless testing: It can run tests in headless mode (Chrome, Firefox) without having to render DOM.
3.	Proxy server: TestCafe uses a proxy server. It injects scripts into the page, which can inspect and control elements on the page. This amazing tool also allows interaction with native alerts, file upload inputs, and iframes.
4.	DB fixtures: The ability to call out to parts of your Node server application directly from the test (setting up and clearing database fixtures, starting and stopping the test server).

https://devexpress.github.io/testcafe/documentation/test-api/assertions/assertion-api.html
https://devexpress.github.io/testcafe/documentation/test-api/actions/