Improve Allure agent mode workflows for scoped test review#700
Merged
Conversation
Allure perf metricsGenerated at:
Artifacts: allure-perf-metrics |
vdvukhzhilov
approved these changes
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allure agent mode now supports a more direct workflow for agent-driven test review. Agents can provide compact inline expectations for expected tests, labels, environments, forbidden scope, and evidence such as steps or attachments, while
allure agent capabilities --jsonand task-oriented help make the locally supported CLI surface discoverable without relying on stale generated instructions.Prior runs are also easier to recover, inspect, and reuse.
latestreports both the output directory andindex.md,queryprovides focused JSON views of summaries, tests, findings, and individual tests, andselect/--rerun-*let agents rerun failed or selected tests through Allure test plan support instead of manually rebuilding runner-specific test names.The reusable skill guidance is now kept version-agnostic, with project-specific and version-specific details moved into generated local guidance and the CLI/plugin documentation. Old in-repo agent-mode skill files and obsolete local agent-mode docs were removed so the CLI remains the source of truth for supported commands.