/
How to Start - DC App Testing
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html' is unknown.

How to Start - DC App Testing

We provide performance testing as a service for Atlassian Data Center (DC) apps (Jira, Confluence, JSM). This testing is fully automated with Selenium and the official atlassian/dc-app-performance-toolkit.


How to Start

1. Go to Our Customer Portal

Access the testing request form by visiting:
πŸ‘‰

2. Raise a Ticket

Submit a ticket requesting DC performance testing for your plugin through the portal. Our team will handle the setup, execution, and report generation.

image-20250407-095524.png

3. Provide Required Details

Fill in all the required fields mentioned in the form (see Information Required Before We Begin).

image-20250407-095858.png

4. Upload Artifacts

Attach your plugin .jar and .obrfile and a zipped version of your dc-app-repo with the relevant test cases.

5. Payment

There are no additional service charges. You are only required to cover the server cost.
Note: Payment must be completed before testing starts.

BEGIN NOW

Β 

Information Required Before We Begin

Please provide the following details when raising the ticket:

Field

Description

Field

Description

Summary

A brief summary of your app and what you're testing

App Group ID

The Maven Group ID registered for your app (from pom.xml)

App Artifact ID

The Artifact ID of your app's JAR/OBR file (from pom.xml)

App Version

The version of the app you want to test (e.g., 1.0.1)

Application

Target platform: Jira, Confluence, or JSM

Environment

Choose production or development

License (optional)

If your plugin doesn’t work with a timebomb license, please provide a valid license key

Attachment

Attach your plugin JAR/OBR and a zipped version of your dc-app-repo with app-specific test cases


Β 

Notes

  1. After each test run, a ZIP archive of the test results is attached to the ticket for analysis and debugging.

  2. Payment must be completed before testing begins.

  3. Prior to testing, in the "Waiting for Review" stage, we run automated validation scripts to verify the provided parameters.

  4. Update the Automation Review status based on result Validation Success or Validation Failed.

  5. Upon successful review, the test progresses based on the selected environment (dev or prod).

  6. If validation fails, the ticket will move back to the "Waiting for Customer" stage.



Related content