From LiquidPubWiki

LiquidPub development is test driven. This means that tests are considered an integral part of the code and the build process. Each testable unit of code will have a test verifying its functionality. We employ unit testing as the basic form of testing. Each unit of code, from the smallest (a single method inside a single class), to the biggest (an entire module) will be tested as a standalone entity. Next, integration testing will to be performed for classes, packages, and modules. To achieve this, we require our developers to write their own test cases and test scripts in order to automate testing procedures. Tests and test scripts will also be kept under revision control.

The description of testing policies might be added here in the future.

Continuous integration

LiquidPub development follows a process of continuous integration of its components. Continuous integration is a set of best practices aimed at reducing integration time for developing a software application. See http://www.martinfowler.com/articles/continuousIntegration.html for a complete description of continuous integration. To support developer usage of these practices we rely on a tool called Cruise Control.

Sandbox instance

The project has is own "test", or "demo" instance, namely a server running the latest beta version of the application. This is publicly accessible, everybody is allowed to play with it. This way people will get familiar with our interface in a safe environment. Plus, as more people start using it, they are likely to spot errors more quickly than by lone developers downloading the code and setting up an instance on their own.