Skip to content

Update stale references to properties #2

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.

Sign up for GitHub

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

Open
bornskilled200 wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Update stale references to properties #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -293,7 +293,7 @@ Notice that if the data set cannot be found in the default location, i.e. testDa

By default DbUnit Express uses a file based Derby database. This is extremely useful when your tests fail and you need to see how has the data changed to understand why they fail. However there may be cases where you would prefer to use another database or a pure in-memory database.

To use an [in-memory Derby][18], set the `connectionUrl` property in the `dbunit-embedded.properties` file described above like this:
To use an [in-memory Derby][18], set the `connectionUrl` property in the `dbunit-express.properties` file described above like this:

dbunit.connectionUrl=jdbc:derby:memory:myDb;create=true

Expand Down Expand Up @@ -447,7 +447,7 @@ Migration from v1.2.0: Rename package from net.jakubholy.testing.derby.embedded
isn't necessary anymore, which is useful e.g. in JUnit 4 or when extending another JUnit
derivation. It's also a standard DbUnit's IDatabaseTester.
(2) It's now possible to change completely the DB used by defining some JDBC
properties in dbunit-embedded.properties
properties in dbunit-embedded.properties (now named dbunit-express.properties)
(3) Added utility methods getDataSource, getSqlConnection and a convenience method
createCheckerForSelect, some of those implemented in the EnhancedDatabaseTesterDecorator
so that they can be added to any IDatabaseTester.
Expand Down