Hi Aleksandar,

Can you please show (attach|) your POM. Maybe your failsafe config is 
non-optimal.
In general: Intellij uses a different kind of junit execution, than 
failsafe/surefire

Kind regards
Robert

> Am 05.01.2019 um 12:20 schrieb Aleksandar Tokarev <a.tokare...@gmail.com>:
> 
> I am having a Spring Boot application with around ~500 Tests (Unit and
> mostly Integration).
> 
> When i start running the tests in IntelliJ with second click -> Run all
> Tests - tests run in around 10-15mins.
> 
> When i try to run the tests with "mvn verify -P itest" in IntelliJ
> terminal, the execution time is around an hour. This is because this
> command starts and stops the Spring Test Runner Server on every class
> (which is not my desired result).
> 
> The IntelliJ second click -> Run all Tests starts it only once. Our Jenkins
> Job is running the tests with "mvn verify -P itest", so my question is how
> can i change this behavior, to start and stop the Test Runner only once
> (with this "mvn verify -P itest" command).
> 
> itest is the profile that we have in our pom.xml which includes the classes
> that contain integration tests (using maven failsafe plugin)
> 
> Here are the annotations of our base abstract Integration Test class
> 
> @RunWith(SpringJUnit4ClassRunner.class)
> @SpringBootTest(classes = MainApplication.class, webEnvironment =
> WebEnvironment.RANDOM_PORT)
> 
> I found this article which could by similar to my problem, but this does
> not explain the behavior that IntelliJ gives me.
> 
> Reset Spring-Boot During Integration Tests
> <https://stackoverflow.com/questions/44241936/reset-spring-boot-during-integration-tests>
> 
> Thanks a lot in advance


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to