Rate this page:
This page describes the performance and scale testing requirements for Data Center apps in the Atlassian Marketplace. Here, we provide guidelines for configuring an existing test platform to produce the test data we need to evaluate your app. For a general overview of Data Center app development, see Developing apps for Atlassian Data Center products.
Don’t have a test platform yet? We can help you set one up:
Going through the approval process for Atlassian Marketplace, requires executing performance tests on the host equivalent in its capacity to our Data Center customers' ones. The test environment is a crucial point that influences test results and shows off performance impact on the software itself. Hence, running performance suites will require a clustered test host with node configuration similar to AWS instance type (8 CPU core and 32 GB RAM).
You're required to run tests with preloaded large dataset to your host. The base dataset must mimic the one that ships with the Data Center App Performance Toolkit. See the datasets outlined below.
|Jira||See the enterprise-scale dataset shape listed on Jira Data Center Load Profile.|
|Jira Service Management||See the enterprise-scale dataset shape listed on Jira Service Management Data Center Load Profile.|
|Confluence||See the enterprise-scale dataset shape listed on Confluence Data Center Load Profile.|
|Bitbucket||See the enterprise-scale dataset shape listed on Bitbucket Data Center Load Profile.|
|Crowd||See the enterprise-scale dataset shape listed on Crowd Data Center Load Profile.|
|Bamboo||See the enterprise-scale dataset shape listed on Bamboo Data Center Load Profile.|
You’re required to conduct performance testing on a 1 node DC instance, with and without your app installed.
Jira: login, create issue, view issue, edit issue, view dashboard, view scrum board, view kanban board, add comment,JQL search, logout.
Jira Service Management: login, view request on portal, create request, view request for agent, edit request, view dashboard, add comment, add attachment, view queues, view reports, JQL search, logout.
Confluence: login, view page, edit page, create page, add comment to page, view blog, create blog, view dashboard, logout.
Bitbucket: git clone via ssh, git clone (via https/ssh), git fetch, git push (via ssh/https), git push (via https/ssh), login, create pull request, comment pull request, view branches, view dashboard, view repo, view project repos, logout.
Crowd: user authentication via crowd.
Bamboo: login, view plans, view plan results, view plan configuration, view plan history, start plans in parallel.
We advise using the specified parameters to establish decent workload for all tests. The key values are outlined below:
: - number of total actions per hour.
: - number of concurrent users for scenario.
: - duration of the performance run.
1 node scenario parameters
2 nodes scenario parameters
4 nodes scenario parameters
In order to pass the DC Apps approval process, you need to attach information that covers following points:
This report should show the response time of each action for two deployments with and without the app installed.
|Action||Without app (timing in ms)||With app (timing in ms)|
The report should show the response time of each action on instances with one, two, and four application nodes.
|Action||1 node (timing in ms)||2 nodes (timing in ms)||4 nodes (timing in ms)|
Rate this page: