Workflow 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.

---

Workflow Stages and Transitions

WAITING FOR CUSTOMER

Initial stage when a customer raises the ticket.

• Customers are expected to provide the required details and attachments (plugin JAR/OBR, dc-app-repo ZIP, etc.).

• No processing is started at this stage.

WAITING FOR REVIEW

Once customer submits the ticket with all inputs.

• Validation scripts are triggered automatically.

• Scripts validate:

  • Plugin metadata (Group ID, Artifact ID, Version)

  • Required files

  • Test configuration values

• The result of this validation updates the AUTOMATION_REVIEW field:

  • ✅ Validation Success – Ticket transitions to READY FOR TESTING.

  • ❌ Validation Failed – Ticket transitions back to WAITING FOR CUSTOMER for fixes
    

READY FOR TESTING

The request is now ready for execution.

• Pre-test configurations are set up based on the environment (dev/prod).
  

IN PROGRESS

The testing job has officially begun.

• Customer details and configurations are extracted.

• Automated test scripts start running based on test type (one-node, two-node, etc.).
  

RESULT REVIEW

Testing has been completed.

• Results are compiled and zipped.

• Customers can download the result ZIP attached to the ticket for debugging and review.

• Ticket is pending customer confirmation or closure.
  

ESCALATED

Triggered manually by agents or automation in case:

• Re-test is required

• Review needs further internal clarification

• Ticket needs elevated attention
  

CANCELED

The ticket was closed due to one of the following:

• Plugin errors that halted execution

• Invalid environment or licensing

• Manual cancellation by the customer or agent

---

---