load

This package provides a set of test cases intended to give information about WfMOpen's load behaviour. Please note the package is under construction. Thus, the current state of the package is a preliminary one.

The tests are implemented as client applications based on jUnit and jUnitPerf. Each test client performs one or more activities each one covered by a jUnit test case and will be executed within jUnitPerf frame. This allows to perform an action a number of times as defined by a repeating factor as concurrently initiated by several users with a pre-defined constant delay (that may be zero).

In addition to the investigations related to this three variances (number of users, repeating factor, delay) there's an additional variance in the structure of the process definitions, which is under investigation, too.

The package contains

• a set of files containing single jUnit test cases
• a set of files containing load test cases using jUnitPerf
• a file AllLoadTests.java that performs all the load tests (if the are correctly defined within the file)

The test cases currently available are:

	Variance	Filename	XPDL Data	Description
	number of activities and transitions	LoadU1R5D0AvTvseq.java	A5nmmT4seq.xml A10nmmT9seq.xml A20nmmT19seq.xml	This test examines the load behaviour depending on the number of activities contained in a process. The activities will not start automatically. Hence, there should not be any interference with running processes. 1 user starts creating a process with 5 activities repeating 5 times 1 user starts creating a process with 10 activities repeating 5 times 1 user starts creating a process with 20 activities repeating 5 times
	process structure	LoadU1R5D0A10T9var.java	A20nmmT19seq.xml A20nmmT19par.xml	This test examines the load behaviour depending on the construction of a process. The activities will not start automatically. Hence, there should not be any interference with running processes. 1 user starts creating a process with parallel successors activities concurrently repeating 20 times 1 user starts creating a process with serial successors activities concurrently repeating 20 times
	repeating factor	LoadU10RvD0A5T4seq.java	A5nmmT4seq.xml	This test examines the load behaviour depending on the number of times a process is started sequentially. The activities will not start automatically. Hence, there should not be any interference with running processes. 10 users start concurrently - each creating a process repeating 5 times 10 users start concurrently - each creating a process repeating 10 times 10 users start concurrently - each creating a process repeating 20 times
	number of concurrent users	LoadUvR20D0A5T4seq.java	A5nmmT4seq.xml	This test examines the load behaviour depending on the number of users concurrently starting a process. The activities will not start automatically. Hence, there should not be any interference with running processes. 5 users start concurrently - each creating a process repeating 20 times 10 users start concurrently - each creating a process repeating 20 times 20 users start concurrently - each creating a process repeating 20 times
	delay	LoadU20R20DvA5T4seq.java	A5naaT4seq.xml	This test examines the load behaviour depending on the number of users concurrently starting a process. Processes with automatically starting end ending activities are used. Hence, there's an influence cuased by additional load of running processes. 20 users start concurrently - each creating a process repeating 20 times 20 users start with a delay of one second - each creating a process repeating 20 times 20 users start with a delay of two seconds - each creating a process repeating 20 times In the first case there's a load starting at once. The processes are doing somewhat. Hence, compared with test as shown above, there's an additional load on the system. In the two latter cases the load is started with a delay. Thus, the system evolves step by step, first inflating followed by a constant load factor, then deflating.

These tests may be executed by using the build.xml file with the default target run in order to execute a single test, e.g.

        ant -Dtest=<value>

where <value> is the classname (without the package name, which will be assumed as systemtest.load.) that contains the required test suite to be executed.

Using the target run-all all the tests may be successively executed following the sequence as defined in AllLoadTests.java.