Compliance tests are not executed about qendpoint HOT 5 OPEN

@hmottestad, It seems that the compliance tests are using Jupiter, but I've never worked with it so I don't know if the issue is coming from it or not.

from qendpoint.

Jupiter is the name for Junit 5. Jerven migrated those tests from Junit 4. I know there is one issue with the way that they are executed now. The lifecycle hooks don't work correctly. Maybe that is the issue here?

from qendpoint.

Maybe surefire/failsafe maven plugins need to be updated to detect the tests?

from qendpoint.

Ok, I've updated that to test in the test-compliances branch, but I get errors, I'll try to see why

https://github.com/the-qa-company/qEndpoint/commits/test-compliances/

from qendpoint.

What's happening now is probably related to the lifecycle issues with the tests. The directory that is created for the new repository is the same for each test, instead of a new directory. So essentially it's starting a repo in a directory, then shutting it down, then starting it back up again. Doing this over and over again should be fine, but I think that qEndpoint probably has some bugs when this happens.

One quick fix would be to create a new directly within the temporary directory, in the new repository method.

from qendpoint.