allure testops

Managing test cases in Allure TestOps manually is prone to silent failures and data loss. This skill provides a rigorous interface for interacting with your TMS, ensuring every write is verified and every test case is properly structured. It handles the nuances of the Allure API that often trip up standard scripts, such as step creation races and complex AQL queries.

What it does

• Manage test cases Create, update, and find test cases with full metadata support.
• Step synchronization Build atomic test steps with persisted expected results using verified multi-call workflows.
• Advanced searching Execute precise AQL (Allure Query Language) queries for custom fields, dates, and issue links.
• Manual launches Orchestrate manual test runs from creation through result triage and defect linking.
• Metadata hygiene Bulk manage tags, external links, and custom field values with ID resolution.

How it works

1. Search and Discovery The agent uses find_test_cases or search_test_cases with RQL to prevent duplicates and find reusable stubs.
2. Atomic Writing It creates test cases then populates steps one at a time to avoid race conditions.
3. Verification Loop Every write operation is followed by a read-back call to confirm the Allure UI actually reflects the changes.
4. Result Triage For failed launches, the agent groups similar failures and links them to defects.

Frameworks & tools

Requires the allure-testops-mcp server. Compatible with any environment using Claude Code or Cursor.

Why this beats prompting it yourself

Writing to Allure TestOps via LLM often results in dropped steps or empty expected results because the API requires specific sequences for data persistence. This skill enforces production-tested workflows that verify every transaction, preventing the silent data loss common with generic prompts.

Use cases

• Drafting and Pushing Converting natural language requirements into formatted test cases with atomic steps.
• Launch Analysis Summarizing failed test results from the last manual launch and filing defects.
• Coverage Audits Searching for existing test coverage before implementing new features to prevent TMS bloat.
• Mass Updates Applying tags or linking Jira tickets across multiple test cases in a single operation.

Known limitations

Cannot delete test case steps or expected results; these must be removed manually in the Allure UI. Parallel writes to a single test case are restricted to prevent data corruption.