This is a classic test debugging scenario. It looks like you’re using a headless browser driver, and it should be noted that this is hard enough to debug locally, never mind remotely! Nevertheless, my advice would be to dig in and debug why they are failing.
In one case, you have an Angular error in your JS app:
TypeError: Cannot read property ‘content’ of undefined\nUndefined states error debug logs:\nRequested state name: Introduction\nExploration ID: Y83LB8ECQe3n
I expect that should never happen, so you need to find out why it happens, and then stop it happening.
There is also an element not found:
No element found using locator
However, that is probably due to the Angular issue.
I am also seeing this:
Page takes more than 15 secs to load
Again, you need to find out why.
For all of these cases, I would suggest:
- Create a branch
- If the tests take a non-trivial time to run through, modify them in the code so they do not run, or just run a single test
- After a (quick) job run on code push, re-run it with SSH
- Use your test runner to run flakey/broken tests individually and debug them on the server
- Use the screenshot feature in your headless browser if needed
- Use a console editor to make more trivial assertions prior to a failing step (e.g. is there any HTML in the DOM at all? Has the UI rendered? etc.)