ActiveJDBC Models are easy to test, and there is a convenience class for opening and closing connections during tests.

Test database for testing

It is customary for JavaLite projects to use one database for testing and a different one for running the system locally. It makers it easy to preserve data in place in the development database, and still use the full power of database access to your test database during tests.

For example, you could have some user data in a development database which will allow you to log in, and perform other operations, and yet you can run test logic against your test database, destroy and re-create any data in it, without having to wipe clean your development database.

DBSpec for database tests

org.javalite.activejdbc.test.DBSpec is a super-class for tests that require a database connection. It is integrated with database file configuration and will automatically open a corresponding database connection before a test execution and close it after the test.

Please, see more on environments on database file configuration page.

Example of a DBSpec test

Lets say we are developing a blog, and we need to persist a post. A post will have title, content and author. All these attributes are required. Here is an example of a model we are testing:

A test will look like this:

Technically speaking, you can use it for any test requiring a connection, but it is also easy to use for Model tests.

Steps of execution

In the test above the DBSpec will:

  1. open a test connection defined in
  2. start a transaction
  3. make connection available during tests
  4. roll back transaction after the test execution to keep the database clean
  5. close the connection

This class allows for tests to run in a clean room environment, since the database tables will always have a clean state for any given test.

Transaction Management

Default transaction management

By default, the test will automatically set your database connection to autocommit = false, hence starting a single transaction. When the test is complete, this transaction will be automatically rolled back.

This is done so that your tests would not leave any remaining data in the database, since it might interfere with other tests and might even generate unpredictable results.

The autocommit = false is a default behavior in all JavaLite tests.

The flag autocommit = false will ensure that the JavaLite test will not attempt to automatically: 1. Start a transaction and 2. Rollback said transaction after the test.

Basically, this flag ensures that the test will be operating with autocommit = false.

Custom transaction management

In some cases, the code that you test, commits transactions. In such cases, rolling back transactions at the end of a test is meaningless, since the database has already been polluted with some data. In such cases you want to manage transactions manually. To do so, you can disable this feature:

The code above turns off any attempts of JavaLite to manage transactions, so you are on your own!

Keep in mind, you will need to manually cleanup the data from the database after the test.

Non-models database tests

While DBSpec is usually used to test models, it can be used to test any code that require a database connection. If you need to get a hold of that connection, you can use class Base:

How to comment

The comment section below is to discuss documentation on this page.

If you have an issue, or discover bug, please follow instructions on the Support page