Evidence and report updates
Use the lightest evidence profile that answers the team's diagnostic needs. Failed runs can retain portable reports, bundles, manifests, and structured checks.
Evidence level profiles
- What it does
- Controls how much SHAFT evidence each run retains through named profiles.
- Why use it
- Balance diagnostic detail, storage, and runtime cost by environment.
- Configure
- Select the documented evidence level in SHAFT properties.
- Use it
- Run a test and confirm the expected attachments are present.
Failure Trace Viewer
- What it does
- Attaches a self-contained failed-test timeline with available DOM, network, console, and locator evidence.
- Why use it
- Inspect a failure without rerunning it or locating sibling assets.
- Configure
- Leave shaft.trace.enabled=true and shaft.trace.mode=auto unless the project needs another profile.
- Use it
- Open SHAFT Trace Report.html from failed-test attachments.
Failure diagnostics bundle
- What it does
- Packages sanitized metadata, bounded logs, and referenced artifacts into shaft-diagnostics.zip.
- Why use it
- Hand one portable evidence bundle to a person or local diagnostic tool.
- Configure
- Enabled by default; set shaft.diagnostics.enabled=false only when required.
- Use it
- Download the failed-test attachment and inspect it with the documented workflow.
Failure brief and attachment manifest
- What it does
- Adds a concise HTML failure brief and a JSON inventory of attached evidence.
- Why use it
- Find the failure summary and every artifact quickly.
- Configure
- No separate setup is needed for normal report generation.
- Use it
- Open SHAFT Failure Brief.html, then follow the manifest to deeper evidence.
Validation, accessibility, visual, and API evidence
- What it does
- Attaches structured evidence for supported assertions, accessibility checks, visual comparisons, and API validations.
- Why use it
- Connect a test verdict to the data that produced it.
- Configure
- Use the corresponding SHAFT validation or audit API and the desired evidence profile.
- Use it
- Open the test attachment beside the failed or passed checkpoint.
Soft verification and checkpoint JSON
- What it does
- Records verification checkpoints in structured JSON while allowing the test to continue to its final verdict.
- Why use it
- Review every collected verification failure instead of losing later checkpoints.
- Configure
- Use verifyThat for soft checks and keep report evidence enabled.
- Use it
- Run the test, then inspect checkpoint JSON and the final aggregated verdict.
Sharded report merge
- What it does
- Combines result artifacts from parallel CI shards into one report input.
- Why use it
- Review one run without losing shard-specific evidence.
- Configure
- Upload each shard result directory with unique artifact names.
- Use it
- Download and merge all shard artifacts before generating the final report.
Backend-neutral offline trace expansion
- What it does
- Expands supported Selenium and Playwright action evidence into the same offline trace surface.
- Why use it
- Use one investigation flow across browser backends.
- Configure
- Keep trace capture enabled for the active backend.
- Use it
- Open the self-contained report and expand the relevant action.
Locator health reports
- What it does
- Records locator score and stability information for locators used during a run.
- Why use it
- Find fragile locators before they become repeated failures.
- Configure
- Set shaft.locatorHealth.enabled=true.
- Use it
- Run the web suite and review the locator health attachment.
Flake and auto-wait profiler
- What it does
- Records flake risk and auto-wait behavior for investigation.
- Why use it
- Separate recurrent instability from a one-off failure.
- Configure
- Set shaft.flakeProfiler.enabled=true and keep shaft.flakeProfiler.failOnSevereFlakeRisk=false until the team approves thresholds.
- Use it
- Run the focused test and review its profiler evidence.
Allure SHAFT overview panel
- What it does
- Adds SHAFT run and evidence context to the generated Allure overview.
- Why use it
- Start report review from SHAFT-specific status and attachments.
- Configure
- No separate setup is needed beyond normal Allure report generation.
- Use it
- Generate the report and open its SHAFT overview.
Native Playwright traces
- What it does
- Retains supported Playwright trace ZIPs beside SHAFT evidence.
- Why use it
- Inspect native browser timing and actions when retry evidence captures a trace.
- Configure
- Keep playwright.tracing.onRetryOnly=true, or enable full-session tracing explicitly when needed.
- Use it
- Open the attached ZIP with Playwright trace tooling.
Keep the default automatic trace profile unless the project needs another level:
shaft.trace.enabled=true
shaft.trace.mode=auto
