Hi folks, bee working through the JS certification path and running into an issue where the Login.e2e test for the example app is failing when run in GitHub Actions , despite consistently passing locally. It’s failing to locate the Projects card-title element after entering the account details and …

@cassandrahl I had a play with your project and had some success. I replaced runs-on in the GitHub workflow file from windows-latest to ubuntu-latest and that caused the tests to pass on a forked version of your repo. I’m not entirely sure why it would be the case that windows fails but ubuntu passe…

Hi @spk Could you try replacing the sleep 10 command with this command: curl --head -X GET --retry 60 --retry-connrefused --retry-delay 1 http://localhost:3000 This can be used to wait for the app to start up in a more robust way. Rather than just waiting for ten seconds in hopes that it will be …

Hello @spk It seems like the test is failing to locate the “.card-title” element after clicking the login button. Check the application code to ensure that the “.card-title” element exists on the page you are navigating to after logging in. Also, If the “.card-title” element is dynamically genera…

Hi sorry for the delayed response, been a hectic week. I did give that a try and unfortunately it still seems to be failing at the same step. I can see from another thread that the same steps did help another user to get theirs passing. Checking the two yml files on the respective forks ( mot-cert-…

Hi @spk So I’ve been taking a look at this and I’m honestly stumped as to why it doesn’t work. This might seem like a bit of a cop out request, but could you try re-running the build and see if it passes upon a second run?

Hey Mark, yeah I’ll give it another shot, I’ve given it a few already but we all know how temperamental CI runs can be :sweat_smile: I’ll rerun with the debug logging enabled too in case that flags anything up EDIT: Woot! :partying_face: Worked this time for Unknown CI Reasons :tm: Update sleep com…

Looking at your pipeline I would say that changing out the command has worked because I can see one test has passed, but the other has not. Try putting await browser.pause(2000) before that call for .card-title to see if the test is moving too quickly before the login process is complete.

Thanks @mwinteringham . I added it, but I’m still getting the same error. And it’s still passing fine when I run it locally.

@mwinteringham Darn, ChatGPT did suggest that, but I was hoping for a more satisfying solution that would let me keep things as close to the example as possible. But I ran the pipeline three times with that, and it passed every time! So thanks for your help.

2.4.2 - Example test failing on GitHub Actions

Discussions

cassandrahl (Cassandra H. Leung) 8 May 2025 14:47 7

Hey @mwinteringham , I replaced the sleep 10 command with your suggestion, but am still getting the same issue. I ran it twice, just to make sure. Here’s my .yml file: mot-cert-support-app-js/.github/workflows/build_test_react.yml at trunk · CassandraHL/mot-cert-support-app-js · GitHub Any other ideas to try?

2.4.2 - Example test failing in pipeline only

Topic		Replies	Views
Running UI tests in github action fails Discussions automation , ui-automation , mot-fcta	6	658	23 February 2024
FCTA_JS: 2.5.3 Github Action activity failed with error Discussions automation , mot-fcta	7	108	30 August 2024
3.3.2: Resolving Failed Checks: GitHub Action failed to run Discussions learning , automation , curriculum-automation , mot-fcta	5	311	5 June 2024
2.4.2 - Example test failing in pipeline only Discussions curriculum-automation , mot-fcta	6	119	19 May 2025
2.4.2 - Build is failing on github but tests passing locally Discussions automation , mot-fcta	3	243	19 March 2024

2.4.2 - Example test failing on GitHub Actions

Related topics