allure testops

    1

    Interface for Allure TestOps to manage test cases, steps, and manual launches with verified write operations.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    allure testops

    Example session with this skill installed

    Search for any test cases related to "User Authentication" in project PROJ-1. If none exist, create a basic smoke test case for the login flow with three steps.

    • Read your context and instructions
    • Compiled the allure testops

    I searched for test cases related to "User Authentication" in project PROJ-1 using keyword variations. No existing cases or stubs were found. I have created a new smoke test case and verified the step persistence.

    Test Case Created: User Authentication Smoke Test

    ID: 4521
    Status: Created & Verified

    StepActionExpected Result
    1Navigate to the login page and enter valid credentials.User is redirected to the dashboard.
    2Click on the profile icon in the top right corner.Profile menu opens showing correct user details.
    3Click the "Logout" button.Session is terminated and user is returned to the login screen.

    Verification Details:

    • get_test_case_steps confirmed all 3 steps persisted.
    • get_test_case_overview confirmed expected results are attached to regularStepIds.
    • Tag smoke added successfully.

    Next steps

    1. Review the test case in Allure TestOps at https://allure.example.com/project/PROJ-1/test-case/4521.
    2. Link the relevant Jira ticket using add_test_case_external_links_bulk.
    3. Assign this case to a manual launch if immediate execution is required.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    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.

    Cannot delete individual steps or expected results via API. Concurrent writes to the same test case are prohibited to avoid data loss. ID resolution for custom fields is required.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Allure Testops MCP
    Node.js

    Permissions

    Write Files
    Read Files
    Environment Variables
    Network Access
    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    Standard AI prompts often fail to persist complex step data or ignore Allure's API race conditions; this skill uses a verified 'write-then-read' loop to ensure every step and expected result is actually saved in the TMS.

    This skill requires the allure-testops-mcp server and is optimized for use within MCP-compliant environments like Claude Code and Cursor.

    Yes, the skill includes advanced support for Allure Query Language (AQL), allowing you to search for test cases based on custom fields, issue links, and specific date ranges.

    While the skill can create and update test cases, it cannot delete steps or expected results; these specific destructive actions must be handled manually within the Allure UI to prevent accidental data loss.

    The skill facilitates manual launch orchestration by creating runs, grouping similar failures, and automatically linking results to external defect trackers like Jira.

    New in Code Quality & Review