How should I structure my GWT integration tests when using Maven?

I am using Maven to create a GWT application. We use the parent module with several submodules in Maven. We decided to make a separate module for integration tests, because it would seem like clapping so that integration tests are separated from unit tests in the same module. But, when we tried to run the GwtTestCase tests from a separate maven module, this turned out to be problematic; in particular, we could not find an easy way to get the test to see the entry point to our application in Eclipse or in Maven.

Is there a good way to structure GWT integration tests when using Maven? Is it best to leave them in the GUI module and try to separate the integration tests from the unit tests using the maven profile?

+4
source share
1 answer

We do not extract integration tests into a separate module

In our project, we do this as follows:

<profiles> <profile> <id>nointegration</id> <properties> <integration.tests.includes>none</integration.tests.includes> </properties> </profile> ... </profiles> 

If we do not want to run integration tests:

 mvn clean install -Pnointegration 

therefore, only a regular test was performed without integration

0
source

Source: https://habr.com/ru/post/1334993/


All Articles