Types of Testing - DC App Testing
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html' is unknown.

Types of Testing - DC App Testing

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


Types of Testing

1. Development Testing

  • Involves a single test stage

  • Runs only your app-specific test cases.

  • Duration: 50 minutes.

2. Production Testing

  • Testing Stages:
    The app goes through 5 test stages:

    1. Pre-Indexing

    2. Post-Indexing

    3. One-Node

    4. Two-Node

    5. Four-Node

  • Test Case Execution:

    • Pre/Post-Indexing: These are not app-specific and run from the official dc-app-performance-toolkit.

    • Node-based Testing (1/2/4 Nodes): These stages run your app-specific test cases.

  • Jira-Specific:
    Indexing stages apply only to Jira (not required for Confluence, as per Atlassian documentation).

  • Duration:
    Each test case runs for 50 minutes.


Recommendation

We strongly recommend conducting a Development Testing run prior to initiating Production Testing. This step ensures that your custom test cases are executing as expected. In our experience, bypassing this validation often leads to test failures during Production Testing, resulting in unnecessary expenditure.


🧩 Summary

Feature

Development Testing

Production Testing

Feature

Development Testing

Production Testing

Environment

Controlled Testing Setup

Full Atlassian DC-like production setup

Test Cases

App-specific only

Official Atlassian cases

Indexing Phases

✅ (Jira only)

Duration

50 min total

~50 min per stage

Recommended For

Pre-check, Debugging

Final performance submission to Atlassian

Cost

💰 Low

💰💰 Higher (multiple stages, full env)

Output

Basic result logs

ZIP of structured reports for submission