Recently we added a new out of the box module called for test-suite for MetCat. It is a workflow publisher client which can emulate workflows and pre-poluate data. So using test-suite, you can emulate heavy workload for MetCat and as well as can be used justify performance metrics.
Test type: run_from_registry
In 0.1 Release of the test-suite, we have integrated only one test-type called run_from_registry. When Test-suite is running a run_from_registry type test case, it takes saved workflow-templates from Airavata Registry, spawn workflows using those templates and submits workflows to a Airavata server to execute in parallel. Here a workflow is an instance of a workflow-template with unique topic ID.
In this test type, test-suite assign each workflow into a separate thread, and assigned in to a fixed size thread pool. So each thread is responsible for executing its assigned workflow. Test-suite is using Airavata Client API to communicate with Airavata Server.
a run_from_registry test can be done in two modes.
In Parallel mode test-suite schedule each workflow template to execute only for N times on separate threads in parallelly and then execute them. Assume there are two workflow-templates are saved in Registry, and you have define the number of repeat times (N), then test-suite will execute total 2N workflows including N from one-template and other N from other template.
In Loop mode test-suite schedule each workflow template to execute for N times on separate threads in parallel and execute them until you terminate the test-suite execution. I am not saying it runs Infinite times, But it will take several years to finish both scheduling and executing workflows in this mode. So when you want to terminate test-suite execution, feel free to press Ctrl + C.
Minimum Work Load
To execute a workflow it takes more time ( simple workflows takes few seconds, but large workflows takes few minutes to hours, days even months...). But to schedule a workflows, it takes only few milliseconds for test-suite. So There is a possibility to generate high workflow load for test-suite by it self. So thread scheduling should be handled carefully, So we introduced a parameter called minimum workload, which defines minimum number of threads should be assigned to the thread pool for execution, before scheduler goes to sleep. when internal load becomes low, scheduler again start his work.
All activities will log and exported into a log file. Please define what you want to log in test-suite property.
you can configure all above disused properties by editing test-suite properties in conf directory in the binary distribution of the test-suite.
We are hoping to integrate several other test types into test-suite in future release.
Building from source
If you are building whole MetCat project using developers' trunk source, test-suite module will automatically build. But if you want only test suite follow following steps.
Check out from svn location http://svn.codespot.com/a/apache-extras.org/metcat/trunk/test-suite
cd to test-suite project folder and type
The compressed test-suite binary distribution is created at
As I mentioned earlier, this is a out of the box module. this will not included in the main binary distribution of the MetCat Server. But if you are building whole MetCat project using developers' trunk source, you can find the binary distribution under test-suite/target directory.
- Start Airavata and export few workflows into Airavata registry. Follow following quick guide to learn how to do that.
An Quick guide to export workflows in to Airavata Registry using Xbaya.
- Setup Registry using, Registry → Setup JCR Registry... ( Simply click OK, if you are using local Jackrabbit server with default configuration. :) )
- Open a sample workflow file or create a workflow as describe in Airavata in 5 minutes tutorial.
- Goto Xbaya → Export → To Registry
- Give a name (This name is used as template ID)
- Tick make public option
- Click Ok.
Back to running test-suite tutorial.
- Unzip test-suite binary file.
- Start MetCat ( follow my previous article )
- Configure test-suite property using testsuite.properties in conf directory.
- Set Airavata related properties using xbaya.properties.
- cd to bin folder.
- Start MetCat Test-suite by executing metcat-server.sh
You can find the test-suite logs under log folder. Finally verify the content captured by MetCat server (Workflows detials) using test-suite log.
In this article, I only focused on to give an introduction to MetCat's test-suite module. I will post a new blog post describing how to do profiling and conduct test cases using test-suite in a later day.