-
Notifications
You must be signed in to change notification settings - Fork 144
HerdDB profile for integration tests #79
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1102,6 +1102,36 @@ | |
</properties> | ||
</profile> | ||
|
||
<!-- Profile for testing with HerdDB --> | ||
<profile> | ||
<id>test-herddb</id> | ||
<activation> | ||
<property> | ||
<name>test-herddb</name> | ||
</property> | ||
</activation> | ||
<dependencies> | ||
<dependency> | ||
<groupId>org.herddb</groupId> | ||
<artifactId>herddb-jdbc</artifactId> | ||
<version>0.22.0</version> | ||
<scope>test</scope> | ||
</dependency> | ||
</dependencies> | ||
<properties> | ||
<connection.driver.name>herddb.jdbc.Driver</connection.driver.name> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what about a plain java test since herddb is java? docker is mainly an additional test to enable to test which looks not needed here, wdyt? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For me docker is also fine. The benefit of a docker image is that you drop it and have a very well defined initial status. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the main problem is about adding more jars in the classpath. I am fine with using in-memory db as well, tests will be probably faster? we should have both. I would start with docker in order to not need to spend time in debugging potential problems about re-initialization of the server There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would dependency:unpack the zip/stack and just launch it with a dedicated classloader (no conflict wth openjpa) |
||
|
||
<connection.url>jdbc:herddb:local</connection.url> | ||
<connection.username>sa</connection.username> | ||
<connection.password>hdb</connection.password> | ||
<jdbc.DBDictionary /> | ||
|
||
<!-- DBCP overrides for testing --> | ||
<dbcp.maxIdle>5</dbcp.maxIdle> | ||
<dbcp.minIdle>0</dbcp.minIdle> | ||
</properties> | ||
</profile> | ||
|
||
<!-- Profile for testing with a custom DB using a system jar --> | ||
<!-- | ||
For example, to test with Oracle, you might run: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you just want to skip this test for HerdDB? In which case you can simply call
setUnsupportedDatabases(HerdDBDictionary.class)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@struberg thanks for the hint.
I wasn't aware of setUnsupportedDatabases
I will rework this patch