2.4.2 Failed GitHub workflow

[erikaandri (Erika Andrijauskaite)]

Hello! I have just started the MoT automation foundation course. In section ‘2.4.2 Adding a Framework to a Pipeline’ I received an error. What could be the reason and how should I solve it?

[christianbaumann]

Do you have a test class named LoginTest?
The error message states that no test class matching that pattern can be found.
Please check the correct spelling, and also upper/lowercase.

[mwinteringham (Mark Winteringham)]

I can see that it is unable access your jarfile. Could the path be wrong? I can see forward slashes in the path to your jarfile.

[christianbaumann]

Stupid me… totally forgot that for me at first it also wasn’t running.

The build jardidn’t match the pattern given in the build_test_maven.yml.
I adapted the run in the Run E2E checks section to java -jar target//mot-cert-support-app-java-*-exec.jar and that did the trick for me.

[erikaandri (Erika Andrijauskaite)]

The issue is still not fixed. I tried a lot of different things but nothing helped. However, I’m receiving a bit different error now:

In class instructions, there was information to create new files in src/test while there was no such folder, only src/main, so I created my files there. Can this be related?

[erikaandri (Erika Andrijauskaite)]

By the way, I also needed to update my yml file from actions/checkout@v3 to actions/checkout@v4 and from actions/setup-java@v3 to actions/setup-java@v4 because I received the following error:

[mwinteringham (Mark Winteringham)]

Thanks for sharing those details.

So I can see your LoginTest file is within the src/main/java part of the project. It needs to be in src/test for Maven to be able to see the file. Create a the folders src/test/java and move the LoginTest class in there.

[erikaandri (Erika Andrijauskaite)]

Still nothing works.

[christianbaumann]

Could you make your repo public and provide the link?
That would make it so much easier to analyse and make the right suggestions.

[mwinteringham (Mark Winteringham)]

@erikaandri I tracked down your repository and took a look at your latest failure and it looks there has been a change in your error. You are now successfully running your test, but it’s failing because it can’t access the app.

My recommendation is to update lines 20 and 21 in your yaml file to the following:

java -jar target/mot-cert-support-app-java-*-exec.jar &
curl --head -X GET --retry 60 --retry-connrefused --retry-delay 1 http://localhost:8080

The first change is an addition of & at the end of the first line. This means don’t wait for the app to run, move onto the next step. The second change replaces the sleep 10 in favour of sending an HTTP request every second to check if the app is up. Once the app is up, we can progress. If the app isn’t up after 60 seconds, it will fail.

[erikaandri (Erika Andrijauskaite)]

Unfortunately, this change didn’t help as well.

trying again

[mwinteringham (Mark Winteringham)]

Apologies I was looking at the wrong part of your YAML. I was offering corrections to the E2E portion of your YAML when it’s this part that is failing:

   - name: Build project and run unit and API checks
    run: mvn --batch-mode package

The reason it’s failing is because you’ve moved your E2E test into an area in which the Unit and API checks are. Meaning it’s getting picked up at the wrong time in your pipeline and ran. It fails because you don’t have the app up and running at that point.

So what you need to do is follow the excludes pattern that is in your POM.xml file (lines 51-53):

<excludes>
   <exclude>**/e2e/**/**.java</exclude>
</excludes>

This is saying any tests that are in the e2e package should be ignored for the Unit and API tests.

In a nutshell, move your LoginTest into a new package entitled e2e and it will be ignored during the Unit and API run. Then you explicitly run it later in the pipeline.