Package com.jcorporate.expresso.services.test

Contains classes that assist in unit testing using JUnit and Cactus testing.

See:
Description

Class Summary

ActionTestServlet	Deprecated. since v5.6, no longer compatible with Struts 1.1
CommandLineParser	Parser class for parsing the command line to get config directory and webapp directory Required arguments: /configDir = /webAppDir =
ControllerTestCase	Base class for testing controllers.
ControllerTestSuite	Test suite that manages schema creation and deletion.
DBTestSuite	Database Test suite that needs a database setup during startup and a schema tear down at completion.
ExpressoTestCase	Base class for Expresso test cases.
SchemaCreator	Given a series of schema class names, this class will perform a "dbcreate" The big difference between this and other versions is that this will work on a blank database.
SchemaDeleter	Class that uninstalls/deletes schemas
SchemaManager	This class reference counts references to various Schema objects.
TestSystemInitializer	This class loads the standard Expresso configuration upon startup.

Package com.jcorporate.expresso.services.test Description

Contains classes that assist in unit testing using JUnit and Cactus testing.

For client side unit testing you should create a single test suite that creates Expresso at the beginning and drops it at the end. You can then use things like DBUnit to create/delete individual entries if needed, but the table creation is just too long for practical testing.

The other class of import is TestSystemInitializer. It allows you to specify a scratch database context that you can use, which, of course, is highly advisable since the unit tests are highly destructive.