I admin I lost in the documentation. E2E tests were quite understandable but not the configuration itself, especially when attempting to replace Karma with wdi5. What I was not able to achieve in the end is to get a coverage report for opa5 tests in BAS + Headless Testing Framework using wdi5. At the same time the ui5-test-runner in Remote mode worked like a charm for me in the same constellation.
Totally understandable - e2e tests also really don‘t benefit from test coverage. That should remain in the integration- and unit-test-realm. Regard e2e testing with wdi5 more like impersonating a user, traveling along the happy- or any other path 😅
I admin I lost in the documentation.
E2E tests were quite understandable but not the configuration itself, especially when attempting to replace Karma with wdi5.
What I was not able to achieve in the end is to get a coverage report for opa5 tests in BAS + Headless Testing Framework using wdi5.
At the same time the ui5-test-runner in Remote mode worked like a charm for me in the same constellation.
Totally understandable - e2e tests also really don‘t benefit from test coverage. That should remain in the integration- and unit-test-realm. Regard e2e testing with wdi5 more like impersonating a user, traveling along the happy- or any other path 😅