git + jenkins + jmeter + Python Integration - Interface concurrent test:
git completion script changes increasing operation, jmeter as script editor complete business needs, jenkins responsible for the script to push the respective shell command to the server and performing corresponding to completion of the performance test, and the statistical results, Python script is responsible for the final result of the transmission message and notifies the nails.
1, automated testing framework process
Script: jmeter script, Python code, etc.
2, software or tools
Git repository: gogs, GitHub, gitlib, cloud code like; other tools SVN e.g.
Build tools: Jenkins, Hudson
Scripting tools: jmeter, Python, LR, VB, etc.
3, check the test environment
1), / data1 directory to check server database table data are in line with the requirements
2) Check each service server is functioning correctly
3), the test script to confirm: get the address http: // ip: xxxx / xxxx / xxxxx.git
Directly to 4, pulling the script, and modify the code
Use git bash scripts and other tools updated file to the git repository
Common statement: git clone http: // ip: xxxx / xxxx / xxxxx.git pull the project from the git repository
git add. add / modify files
git commit -m "aa" submit (comment must have)
git push submit changes
5, the number of concurrent modification and test execution time
To modify the preset data and information related to server configuration information
After jmx script if necessary information is modified, modify the script finished, do not forget to submit updated information to the git repository
6, jenkins build tasks
Task processing, the script execution jmeter
Partial results (shown below): Detailed view from statistical process on jenkins
7, jenkins build tasks
The results obtained script: directory server /root/apache-jmeter-3.2/apache-jmeter-3.2/bin/html.tar.gz corresponding document can be downloaded to the local decompression to obtain the final result is sent by a python script or perform the final test results
Remarks:
As long as there is a modification submitted by GOGS trigger jenkins built directly: Warehouse Settings -> Manage WEB hook -> Add WEB hook, as long as there are changes in git directly trigger a build jenkins tasks:
PUSH address Fill rules: http:? // <Jenkins address> / gogs-webhook / job = <your name Jenkins task>
Successfully tested as shown above.