Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use maven-failsafe-plugin to handle integration tests #305

Merged
merged 1 commit into from
Sep 1, 2022

Conversation

arteymix
Copy link
Member

See #293 for more details

<version>3.1.2</version>
<executions>
<execution>
<phase>process-resources</phase>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pre-integration-test phase could be used for this, although it would be redundant if the model haven't been changed.

<configuration>
<driver>com.mysql.cj.jdbc.Driver</driver>
<username>${gemma.db.build.user}</username>
<password>${gemma.db.build.password}</password>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be better to introduce gemma.testdb.user and gemma.testdb.password for this instead of reusing credentials.

<goal>execute</goal>
</goals>
<configuration>
<url>${bootstrap.db.url}</url>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, a gemma.testdb.bootstrap-url might be a better choice.

<goal>execute</goal>
</goals>
<configuration>
<url>${gemma.testdb.build.url}</url>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace this by gemma.testdb.url, simply.

<configuration>
<argLine>-Dlog4j1.compatibility=true</argLine>
<includes>
<include>**/*Test.java</include>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add **/*IntegrationTest.java here as well?

@@ -71,7 +71,8 @@
/**
* Retrieve all {@link AnalysisResultSet} matching a set of criteria.
*
* @param datasets filter result sets that belong to any of the provided dataset identifiers, or null to ignore
* @param datasets filter result sets that belong to any of the provided dataset identifiers, or null to
* ignore
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unrelated...

@arteymix arteymix force-pushed the feature-use-failsafe-for-integration-tests branch 2 times, most recently from 9d0668b to 03efc49 Compare March 15, 2022 21:47
@arteymix arteymix added this to the 1.28.0 milestone Apr 22, 2022
Only include tests marked by the UnitTest category for
maven-sure-fire-plugin.

Include all test ending with Test.java and exclude those marked by the
UnitTest category for integration tests.

Use integration-test and verify goals for maven-jasmin-plugin as it
require a fake browser.
@arteymix arteymix force-pushed the feature-use-failsafe-for-integration-tests branch from 03efc49 to 740f871 Compare September 1, 2022 21:56
@arteymix arteymix modified the milestones: 1.28.0, 1.29.0 Sep 1, 2022
@arteymix arteymix merged commit 243e5b4 into development Sep 1, 2022
@arteymix arteymix deleted the feature-use-failsafe-for-integration-tests branch September 1, 2022 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant