Activiti Hudson: http://184.108.40.206:8080/
Activiti Bamboo on Codehaus (deprecated): http://bamboo.ci.codehaus.org/browse/ACT
All activiti developers have permission to start a new build manually.
Running the database tests
Goal: run the test suite against a specific database.
Specify properties in command line:
Alternatively, you can specify the properties in a local file. This information goes into a file called 'mysql.properties'. Please create the following folder structure:
Within this directoy create a new file mysql.properties like this:
Running the upgrade tests
Running the server tests
Running QA tests
Tested database systems so far are:
- MySQL 5.1
Setup / Configuration
The following lines will guide you through running the test suite. For this example we will use MySQL 5.1 as database environment. If you would like to run the test suite against a yet unsupported database environment, consult the[Developer Guide - Adding support for new database systems|ACT:Developers Guide].
- Checkout activiti project from SVN
Before you can run the test suite, you need to [checkout activiti|http://docs.codehaus.org/display/ACT/Developers+Guide#DevelopersGuide-Buildingadistribution]. The qa tests are located in the projects 'activiti-engine' and in 'activiti-engine-examples', but you do not need to start them from there separately. You will start the tests from the quality assurance project. But before we have to create a new database schema and user.
* Create a new schema and user
First we need to create a new schema and a new user for the database connection. We set the schema name to 'activiti'.The users name and password are 'qa'! If you need guidance on how to create a new schema and user for MySQL, please consult their [documentation|http://dev.mysql.com/doc/]. Now we need to make sure that the test suite gets a database connection.
* Create a database connection file Run the test suite
Now we are ready to run the qa script. Navigate to /activiti/trunk/qa/ci and run the script that is suitable for your operating system like this:
If you would like to run the qa script against H2, then you need to execute this command: