io.reactivex.exceptions.UndeliverableException from com.epam.reportportal.service.LaunchImpl about agent-java-testng HOT 2 CLOSED

@7vga Every agent in ReportPortal was designed to handle one Launch per execution because we close and free all resources we use on the Launch end. When you call TestNG.run several times it does not initialize our listener a new and uses old one. From pure TestNG prospective this is unrealistic case. Even if you configure your build system to run the same tests with different number of parameters each time it will be separate processes. There are good reasons why they not doing it in the same process. And the first of them is that tests and test frameworks usually not designed to be resilient in the long-running term. Or you have to pass performance profiling phase each test release, that's ridiculous.

So no, you can't do what you described with ReportPortal. That's official. Please configure your build system to run your tests with different set of parameters instead of your own application implementation.

from agent-java-testng.

Got it, thanks for clear explanation, will use other approach

from agent-java-testng.