Test Management Platform for Automation
Once downloaded, unpack the compressed folder to see the structure of (the compiled) TestMP. You'll see a structure like this:
testmp/
|-- bin/ # contains the scripts for startup & maintenance.
|-- conf/ # contains the configuration file.
|-- data/ # contains the database files.
|-- lib/ # contains the TestMP client libraries.
|-- log/ # contains the generated log files.
|-- webapp/ # contains the wars of WebConsole and DataStore.
|-- README.md
It's not forced but recommended that you set the TESTMP_HOME environment variable, of which the value is the path to the testmp/, if you hope to launch TestMP outside such directory.
Before running TestMP, you also need to have Java Runtime Environment (Version 6 or the above) installed, and make sure the JAVA_HOME is set correctly.
You will find most TestMP configurations in the conf/testmp.properties:
# The locale setting of webconsole and reports
locale=en_US
# The launching url of the datastore each for test case, data, and environment.
testCaseStoreUrl=http://localhost:10081/DataStore.do
testDataStoreUrl=http://localhost:10082/DataStore.do
testEnvStoreUrl=http://localhost:10083/DataStore.do
# The number of threads for running tasks.
executionThreadNum=10
# The timeout of task execution. 0 means no timeout.
executionTimeout=0
# The time gap (in seconds) between two refreshings of the task schedule.
scheduleRefreshingTimeGap=1800
# The maximum latency (in seconds) to trigger a scheduled task, or ignore it.
taskTriggerMaxLatency=600
# The default recipient list and subject of the test metrics report.
testMetricsReportRecipients=
testMetricsReportSubject=
# The default recipient list and subject of the test env status report.
envStatusReportRecipients=
envStatusReportSubject=
# The default SMTP settings to sending the report.
smtpSettingHost=
smtpSettingPort=25
smtpSettingUser=
smtpSettingPass=
smtpSettingSTARTTLS=true
Currently TestMP supports UI languages of US English (the default) and Chinese. Change the locale to zh_CN if you want to change the language to Chinese.
While most of the other settings can be left to their default values, testCaseStoreUrl, testDataStoreUrl, testEnvStoreUrl may need to be modified if the default listening ports have been occupied or they are launched remotely.
It's also possible to make these urls the same to share only one datastore. But in practice it will not be efficient and may cause confusion.
The settings of *ReportRecipients, *ReportSubject, and smtpSetting* are for your convenience. You can always input/modify them manually on the TestMP Web Console.
Now we're ready to startup the TestMP!
-
On Windows
cd TESTMP_HOME/bin startup.bat [port] -
On Linux / Mac
cd TESTMP_HOME/bin ./startup.sh [port]
The argument port is optional. If it is not given, the Web Console will defaultly use 10080 as the listening port. Then you may see the output like this:
launching testCaseStore on 10081
launching testDataStore on 10082
launching testEnvStore on 10083
launching TestMP web console on 10080
...
2013-07-04 14:26:55.634:INFO:oejs.AbstractConnector:Started [email protected]:10080
which meanse the datastores for test case, data, and environment, and the web console are successfully and fully launched.
Open your favorite browser, enter "http://the_name_or_ip_of_your_host:10080" in the address bar and click Go. You see the the welcome page on the TestMP Web Console? Congratulations!
Everything in automation code
Document test cases just in code, and no longer bother to maintain them in another place.
The web console will instantly update test document and measures upon test run.
Evaluate the automation test
Test robustness, effectiveness, and efficiency are evaluated into a clean but meaningful report.
You can signoff the report by marking "Accept" or "Refuse" and send it to the stakeholders!
Avoid the data assembling
You can add test data into the data store, categorize it by tags, and use it by API in automation.
Test data is fetched as its original type, or by merging different snippets together.
Leverage distributed scripts
Environment tasks are defined, scheduled, and bounded to scripts on local/remote hosts.
Task executes concurrently, of which the result can be traced on the Web Console.
Copyright © 2013 Zhaowei Ding