rest-assured | Java DSL for easy testing of REST services | REST library

Further research confirmed my theory about the thread-safety issues. I was able to conclude that the issue has nothing to do with SoftAssert and everything to do with rest-assured not being thread-safe. That information can be found here --> https://github.com/rest-assured/rest-assured/pull/851

I was able to find a thread-local branch in which someone kindly did the work to make rest-assured thread-safe. I downloaded 2 files RestAssuredThreadLocal and RestAssuredThreadLocalImpl which can be seen here --> https://github.com/rest-assured/rest-assured/commit/3307ba6c79c5547e88cea286d38e5c8a6d679229

After downloading those 2 files, there were some errors that needed resolved and some deprecated methods needed replaced. After that I was able to successfully run my rest-assured tests in parallel with TestNG with the correct results.

Having public static variables is not a good idea. In addition, the Response variable in RestUtil has no relationship to the one in MyClass, so it is null. A better approach is to pass the Response into your util method such as:

Find the solution for parallel execution with cucumber 7 and serenity junit 4. Below pom.xml is tested and working to execute parallel. According to this pom.xml to execute two ways:

1. locally - add to your runner in tags tag you want to run and then execute this command mvn clean verify

2. mvn clean verify -Dtags="@yourtagHere"

Working pom.xml:

That won't work with @QuarkusIntegrationTest, because this test actually executes the produced JAR and therefore the resources are loaded from inside the JAR itself and not the filesystem.

This code would solve your problem:

You should remove all occurences of cucumber artifacts from your pom. Serenity artifacts already have dependencies to the required cucumber versions. The lates supported version is 6.11.

When you put the same artifact of different version to your root pom, you override that. Hence there is version inconsistency take the place.

Your question topic is unrelated to your question. But, you can use simple function to achieve your goal.

Allure jenkins install config

I found the answer by myself, this is some kind of issue in fresh versions of allure-commandline, try to :

1. install old version, for instance 2.8.0
2. then you could install any new version

Seems like in old version, while installation, it's creating path(for ubuntu in my case) in correct direction, and then just update with a new one... Or you can insert installation directory manually and initially install a new version

RESTEasy, and the quarkus-resteasy extension, don't know what Uni is and cannot serialize it properly.

If you can, I'd advice you to switch to quarkus-resteasy-reactive (and quarkus-resteasy-reactive-jackson) if you're using reactive types.

If you need the classic RESTEasy, add quarkus-resteasy-mutiny to your dependencies.