Thanks for all of your responses! 
Yes that would be a priority too.
Here is a quick update on the current state:
-
Tests are fixed. Distribution 3.x E2E and scheduled tests on GitHub are passing now. The next step is to enable the pipeline to run on commits.
-
I was able to run E2E tests against a PR. Link
However, it took 38 mins to run the GitHub action (16 mins to spin up the container, 17 mins to run tests, and 5 mins for other tasks) We can decrease the time by either
- run it on bamboo (not sure how to run a bamboo plan with a PR)
- or configure tests to run without a container in GitHub.
- run on bamboo, run tests parallelly
- run on GitHub without a container, run tests parallelly
My rough time estimation for each above options are
- 17 min (the container spins immediately )
- 17 min (no need for a container)
- 4 min (tests runs parallelly; est. time = max(time taken by a spec))
- 4 min (same as above)
-
Currently I’m trying to evaluate Cypress and Playwright. We are using both tools right now; playwright for offline tests and cypress for other tests. Both tools provide the same functionality, but Cypress has some issues with offline testing. Tests were already implemented with cypress when the offline testing requirement came. That’s the reason for having two tools. Btw, I found a nice comparison.
