Docs integration

  • Total activity 73
  • Last activity
  • Member since
  • Following 0 users
  • Followed by 0 users
  • Votes 0
  • Subscriptions 53

Activity overview

Latest activity by Docs integration
  • Docs integration created an article,

    How change validation works

    Change validation tells your pipeline whether a code change can move forward at each stage of your workflow, from a pull request through the merge queue to a deployed commit. At each stage, mabl ru...

  • Docs integration created an article,

    2026/11/16 - Chat with the mabl agent beside any page

    You can now get help from the mabl agent without leaving the page you're working on. Click Chat in the top bar to open a side chat with suggestions that fit what you're looking at, such as the plan...

  • Docs integration created an article,

    2026/11/12 - Record mabl plan run results in Azure Test Plans

    Teams that track testing in Azure DevOps can now see mabl results in Azure Test Plans. When we released the Azure Boards integration in October, it filed work items from failed runs and built tests...

  • Docs integration created an article,

    Record mabl results in Azure Test Plans

    With the Azure Boards integration, mabl can record plan run results in Azure Test Plans, next to your team's manual results. Your test plan's progress charts and reports then include mabl's automat...

  • Docs integration created an article,

    Work with Azure Boards work items

    With the Azure Boards integration, you can create work items from failed mabl test runs, link tests to work items that already exist, and use work items to build new mabl tests. This article explai...

  • Docs integration created an article,

    How mabl records results in Zephyr

    When mabl syncs a plan run to Zephyr, what does it write to your test cycle, and what does it leave alone? This article explains where each result goes, what an execution contains, and what happens...

  • Docs integration created an article,

    2026/11/10 - Send each plan's results to its own Zephyr test cycle

    Teams that integrate their mabl results with Zephyr can now link their mabl plans to a specific test cycle in Zephyr. Until now, mabl either created a new test cycle for every plan run or sent ever...

  • Docs integration created an article,

    2026/11/19 - Validate every pull request and deployment with change validation

    You now have more control over how mabl tests a code change at each stage of your workflow, from opening a pull request to deploying to staging. With change validation, you choose the suites that a...

  • Docs integration created an article,

    Run change validation from your own CI

    Run change validation from the CI pipeline you already have. Your pipeline tells mabl when a pull request or deployed commit reaches a stage in your policy file, and mabl runs that stage's suites a...

  • Docs integration created an article,

    Set up a mabl policy file

    If your team uses change validation, the mabl policy file, .mabl/policy.yaml, decides which tests mabl runs when a code change reaches each stage of your workflow, and which failures block the chan...