The Data Center App Performance Toolkit extends Taurus which is an open source performance framework that executes JMeter and Selenium.
This repository contains Taurus scripts for performance testing of Atlassian Data Center products: Jira, Jira Service Management, Confluence, and Bitbucket.
-
Supported Jira versions:
- Jira Long Term Support release:
8.13.3
,8.5.11
- Jira Long Term Support release:
-
Supported Jira Service Management versions:
- Jira Service Management Long Term Support release:
4.13.2
,4.5.10
- Jira Service Management Long Term Support release:
-
Supported Confluence versions:
- Confluence Long Term Support release:
7.4.6
- Confluence Platform release:
7.0.5
- Confluence Long Term Support release:
-
Supported Bitbucket Server versions:
- Bitbucket Server Long Term Support release:
7.6.2
,6.10.7
- Bitbucket Server Platform release:
7.0.5
- Bitbucket Server Long Term Support release:
In case of technical questions, issues or problems with DC Apps Performance Toolkit, contact us for support in the community Slack #data-center-app-performance-toolkit channel.
- Python 3.6-3.8 and pip
- JDK 8
- Google Chrome web browser
- Git client (only for Bitbucket Server)
Please make sure you have a version of Chrome browser that is compatible with ChromeDriver version set in app/$product.yml file (modules->selenium->chromedriver->version).
If a first part of ChromeDriver version does not match with a first part of your Chrome browser version, update Chrome browser or set compatible ChromeDriver version in .yml file.
Make sure that you have Python (see dependencies section for supported versions), pip, and JDK 8 installed:
python3 --version
pip --version
java -version
For Bitbucket Server check that Git is installed:
git --version
We recommend using virtualenv for Taurus.
- Install virtualenv with pip:
pip install virtualenv
- Create new virtual env with python3:
virtualenv venv -p python3
- Activate virtual env:
source venv/bin/activate
- Install dependencies:
pip install -r requirements.txt
Make sure you have Python (see dependencies section for supported versions), pip, and JDK 8 installed:
python --version or python3 --version
pip --version
java -version
Microsoft Visual C++ 14
Windows 10 SDK
For Bitbucket Server check that Git is installed:
git --version
Make sure you have Visual Studio build tool v14.22 installed. Otherwise, download it from Microsoft Visual C++ Build Tools: and do the following:
- Select Tools for Visual Studio 2019.
- Download and run Build Tools for Visual Studio 2019.
- Select the C++ build tools check box.
- Select the MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.22) check box (clear all the others).
- Click Install.
Setup Windows 10 SDK
We recommend using virtualenv for Taurus.
- Install virtualenv with pip:
pip install virtualenv
- Create new virtual env with python3:
virtualenv venv -p python
- Activate virtual env:
venv\Scripts\activate
- Install dependencies:
pip install -r requirements.txt
Get latest codebase from master branch:
git pull
Activate virtual env for the toolkit and install latest versions of libraries:
pip install -r requirements.txt
Official Taurus installation instructions are located here.
The Data Center App Performance Toolkit includes some simple usage analytics.
We collect this data to better understand how the community is using the Performance Toolkit, and to help us plan our roadmap.
When a performance tests is completed we send one HTTP POST request with analytics.
The request include the following data, and will in no way contain PII (Personally Identifiable Information).
- application under test (Jira/Confluence/Bitbucket)
- timestamp of performance toolkit run
- performance toolkit version
- operating system
concurrency
andtest_duration
from$product.yml
file- actual run duration
- executed action names and success rates
- unique user identifier (non PII)
To help us continue improving the Toolkit, we’d love you to keep these analytics enabled in testing, staging, and production. If you don’t want to send us analytics, you can turn off the allow_analytics
toggle in $product.yml
file.
Navigate to docs folder and follow instructions.