Versions Compared

Old Version 63

changes.mady.by.user David E Tanner

Saved on

compared with

New Version 64

changes.mady.by.user David E Tanner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel

Quick Links to:

Table of Contents
minLevel3
Panel

Definition

In our applications and framework, we have used the term "integration test" to describe a written JUnit test case that requires a full Spring context (including all the framework classes), and actually talks to the MITSIS Oracle database. An integration test is disctinct from a pure unit test, which typically uses mock objects for dependencies, and does not talk to the database. We mainly use integration tests for testing DAO classes, but they could possibly be used also for testing service classes and MVC controllers.

Panel

History

Up until now (July 2012) our integration test cases (mainly used for testing DAO classes) have extended a base class BaseTransactionalIntegrationTest, which in turn extends deprecated Spring classes.This base class provided unit tests with a default Spring context and an automatic rollback capability. Unit tests extending this base class were automatically database-aware, and any updates done in the unit test were automatically rolled back at the end of the test.

Panel

The CSF AbstractIntegrationTestBase.java unit test base class

The CSF abstract class is to be used with all integration tests.  It replaces the following deprecated classes

  • BaseTransactionalIntegrationTest
  • AbstractTransactionalDataSourceSpringContextTests
  • BaseSecurityTransactionalIntegrationTest

that were used in csf-common-legacy.

...