- Overview
- Quickstart
- Trust and compliance
- Governance
- Features
- Cartographer
- Delegate for Testing
- Delegate for Testing overview
- Settings for the Testing profile
- Skills for testing
- Routines for testing
- Operations for testing
- Executing manual tests
- Analyzing test automation failure
- Summarizing nightly executions
- Authoring and maintaining test cases
- Automating smoke suites
- Testing with Jira integration and reporting
- Reference
- Troubleshooting
Draft test cases from Jira tickets, log bugs from failed executions, and assemble sprint coverage, sign-off, and QA metrics reports with Delegate.
Once connected, Delegate can read Jira tickets, log bugs from failed runs, and assemble reports that cross-reference Jira and Test Manager. The tasks below are independent from one another.
Prerequisites
- Complete the one-time setup in Setting up and running your first test case.
- Connect Jira (one-time setup):
- Open Delegate → Settings → Connections.
- Find Jira in the list and select Connect.
- Authenticate with your Atlassian account.
- Select your Jira instance or workspace.
Reading a ticket and drafting test cases from it
- Enter a prompt referencing the ticket, for example: "Read ticket MYAPP-42 and write me a test case for each acceptance criterion."
Result
Delegate pulls the ticket's title, description, acceptance criteria, and comments, identifies each criterion, and drafts a structured test case (steps and expected results) per criterion. You will see one draft test case per acceptance criterion, ready for you to review and adjust for your specific UI before adding it to Test Manager.
Delegate only knows what is in the ticket. If the acceptance criteria are vague or missing, the drafted test cases will reflect that.
Logging a bug from a failed execution
- After a failed run, enter a prompt describing the failure, for example: "Create a Jira bug in project MYAPP for the failure on step 3 — the dashboard did not load after login."
Result
Delegate pre-fills the ticket: summary from the failed step, description of observed versus expected behavior, the test case name and ObjKey, a link to the Test Manager execution, and the failing step detail. You will see the new ticket, ready to send to the dev team. Add priority or labels in the same prompt, for example "mark it High priority and label it regression."
Generating a sprint test coverage report
- Enter a prompt naming the sprint and project, for example: "Generate a test coverage report for sprint 24 in project MYAPP."
Result
Delegate pulls the sprint's Jira tickets, finds linked test cases in Test Manager, checks which were executed, and summarizes pass/fail per story. You will see a table of stories with their test case count, execution status, and result, with stories that have zero test coverage flagged explicitly.
Preparing a QA sign-off document
- Enter a prompt describing the release and its sources, for example: "Prepare a QA sign-off document for the v2.4 release. The sprint tickets are in Jira project MYAPP sprint 24. Our test results are in Test Manager project MYAPP."
Result
Delegate pulls release scope from Jira, finds linked test cases and results, identifies tested versus untested areas, and drafts the full document: scope, coverage summary, execution results, outstanding bugs, risk assessment, and a sign-off statement. You will see a complete draft, typically in about 5 minutes, which you can ask Delegate to save as a Word document, a Confluence page, or email directly.
Comparing results across sprints
- Enter a prompt naming the test set and sprint range, for example: "Compare test results for the Regression Suite across the last 4 sprints in project MYAPP."
Result
Delegate aligns results by test case across the sprints and flags patterns: consistently failing cases, flaky cases, declining pass-rate trends, and untested areas. You will see a per-test-case trend table with a status flag (Stable, Flaky, Degrading, Not run, Chronic failure) for each.
Building a QA metrics page
- Enter a prompt naming the project and sprint, for example: "Build a QA metrics page in Confluence for project MYAPP covering sprint 24."
Result
Delegate pulls pass rate, coverage rate, open bugs, and flaky test counts from Test Manager and Jira, and creates a structured Confluence page. You will see a shareable Confluence page with a summary table, trend data, top failing test cases, and coverage gaps, refreshable each sprint with a follow-up prompt such as "Update the QA metrics Confluence page for sprint 25."
Drafting a QA strategy document for a new project
- Describe the new project, for example: "Write a QA strategy document for a new project called NEWAPP — it is an e-commerce platform, 5-person QA team, using Test Manager and Jira, targeting a 3-month delivery cycle."
Result
Delegate drafts the standard structure: scope, approach, tools/environment, test case management, execution plan, entry/exit criteria, defect management, risks, and roles. You will see a roughly 80% complete document; fill in the project-specific scope, team names, and release gates. Starting with just the scope section first tends to anchor the rest well.