---
name: augment-testrun
description: >
  This skill should be used when the user wants to extend/augment a Testiny release test run against the release artefacts (changelog, code changes, ...)
  Suggest what to verify on the existing test cases and highlight release changes that are not yet covered.
---

# Augment a Test Run with Release-Aware Verification Guidance

Cross-reference a release's changes against the test cases in a Testiny test run. For each
existing test case, add a focused "what to verify" comment tied to the actual changes; then
report which changes have no coverage.

## Prerequisites

- You need a source-code MCP server (e.g. GitLab MCP) and the Testiny MCP server. Without them, cancel the skill.

## Step 1: Establish scope

- Resolve the test run and project the user means.
- Determine what the release covers: the release notes (e.g. a work item or changelog provided by the user) and the code changes
  since the last release tag.

## Step 2: Understand the changes

Summarize what changed and where.
- Prioritize user-facing and behavioral changes
- Flag risky refactors as regression risks.

## Step 3: Read the run

Get the test cases in the run — their titles/content/steps, as well as the results, and existing comments.

## Step 4: Map and confirm

- Map each test case to the changes that touch its area and what could regress.
- Identify changes with no test case in the run.
- Before writing, confirm with the user: post comments to Testiny vs. present text only, and
  whether to also flag gaps.

## Step 5: Comment existing test cases

Add a focused comment per test case:
- prefix the comment with the release version (e.g. `v1.42.0 focus:`)
- the relevant change, linked to the source-code host — construct the links from the source-code MCP
  (e.g. GitLab: for a commit that belongs to a merge request, append `/diffs?commit_id=<sha>`
  to the merge request's `web_url`; for a commit without a merge request, use the commit's own `web_url`)
- concrete things to verify
  (prefer bulletpoints over long sentences)
- each comment is self-contained (no cross-references to other comments)
- if a test case already has an augment comment for this release, update or skip it — do not post a duplicate
- if you do not see a reason, why the testcase is in the testrun, also add that as a comment. 
  Comment and reason, why you think the test case is not touching any of the changes.

### Example

```
**v1.x.x focus**: some change (658fcf29c) rewrote sample.ts — consider this and that.

Verify:
* thing A
* thing B
```

```
**v1.x.x focus**: 
* some change (658fcf29c) rewrote sample.ts — consider this and that.
* some other change (02cc01b66) added feature Y — consider this and that.

Verify:
* thing A
* thing B
```

## Step 6: Report missing coverage

If confirmed in Step 4, report uncovered changes as a prioritized list of recommended testing areas.
- For each uncovered change, suggest the area
- Report only, do not create test cases in Testiny.