Closed ghost closed 3 years ago
Can't you use the same client testing tool that the main generator uses? I'm not sure why a backend framework would need to override this.
Hi @mraible , yes in fact the the issue is to apply protractor also for backend. The added title ("or onother tool") is to keep open the investigation if there is another tool more performant for nodejs.
@mraible, excuse me, now for the unit and e2e backend tests there is jest, so it is only required to add protractor as default in the generation for the client side (now the e2e client tests are not generated).
Hi @mraible . Finally I'm able to reach this feature. There is a lot of stuff done (I had to implement the user management api, fix nestJS routing with angular/react, run the e2e tests for admin and entities, create new tests and jobs for every combination in the pipelines).
Please check it. Every improvements and suggestions are welcome!
$200 bug bounty claim: https://opencollective.com/generator-jhipster/expenses/28939
Add default choose for client e2e tests