current disadvantages with protractor:
- async/await for all protractor methods / tests (async await hell, 1 method async/await → every method async/await)
- no video capturing out of the box during ui-tests
- debugging ui-tests on ci only via work arounds: adding source code for taking screen shot (failing tests not reproducible locally on dev)
Advantanges with cypress
+ video capturring out of the box
+ screenshot made on failure out of the box
+ more comfortable with test-runner with hot-reloading, debugging options etc.
To be cleared
? less flaky ui-tests
? open/Beta feature for supporting Firefox on different OS
? return-on-invest
? make sense first for jhipster-module
hipster: new frameworks ?
no
We already started the discussion for Vue.js
But to achieve it completely, it's a lot of work, so not sure we'll be done in the next months.
@geyuqiu : maybe you don't know, but we all work on JHipster during our free and personal time, the evening or the week-end. We are not paid for what we do. It's not our main Job.
So it's hard to code all feature requests or enhancement without help. So if you suggest something, be ready to take the lead and start to contribute to the project.
@geyuqiu I don't understand the "async/await" hell. For me it's not a big issue.
But as @pascalgrimaud said, let's keep one ticket for this in Vue.js, everything is in there.
Most helpful comment
We already started the discussion for Vue.js
But to achieve it completely, it's a lot of work, so not sure we'll be done in the next months.
@geyuqiu : maybe you don't know, but we all work on JHipster during our free and personal time, the evening or the week-end. We are not paid for what we do. It's not our main Job.
So it's hard to code all feature requests or enhancement without help. So if you suggest something, be ready to take the lead and start to contribute to the project.