Which Test Cases Are Affected When a Requirement Changes?
The question every QA lead asks after every scope change, and the reason traceability matrices exist. An agent connected to BesTest over MCP answers it in seconds, with the reasons attached.
The change is easy. Finding its blast radius is not.
A requirement gets updated on Tuesday. Somewhere in your library there are test cases that still check the old behavior: they will pass, and they will be wrong. Finding them means opening the requirement, walking every link, opening every linked test case, and reading its steps against the change.
So in practice it happens rarely, late, or not at all, and the traceability matrix everyone exported last quarter quietly goes stale. This is the single use case our customers bring up most when they hear "MCP".
The manual walk
- Open the requirement, list its linked test cases by hand
- Open each test case and read the steps against the change
- Ping whoever wrote them to double-check your guess
- Update the spreadsheet matrix, which is stale again by Friday
The agent walk
- Ask the question in one sentence, with the change described
- The agent walks the live links and reads every affected test case
- You get the affected list with a reason per test case
- Say "update them" and it drafts the step changes for your review
One prompt, start to finish
REQ-118 changed: the password policy now requires 12 characters instead of 8. Which test cases are affected, and which of them need their steps updated?- 1
Reads the requirement and its links
Over the BesTest MCP, the agent pulls REQ-118, its acceptance criteria, and every test case linked to it through your live traceability, not a stale export.
- 2
Reads every linked test case against the change
It goes through each test case’s steps and expected results and checks them against the new 12-character rule, the reading a human would need an afternoon for.
- 3
Reports the blast radius, then offers to fix it
You get a list: which test cases still assert the old policy, which are unaffected, and why. Approve, and it drafts the updated steps as changes for you to review. Nothing is changed behind your back.
The result
Requirement changes stop silently rotting your test library. The links you already maintain in BesTest become something that answers questions, and significance-weighted coverage tells you immediately if the change opened a real gap.
More prompts to steal
List every requirement changed this sprint and the test cases linked to each.
Which High-significance requirements lost coverage in the last two weeks?
REQ-77 was split in two. Propose how its linked test cases should be re-linked.
Scoped to your permissions, granted per user
Your agent acts as you: everything it reads or writes stays inside your Jira permissions. The MCP is in closed beta while we harden it, with GA coming. The request form asks for a few details from BesTest’s Project Settings in your Jira, which is what lets us enable exactly your site and user.
Request beta accessFrequently asked questions
Does the agent change my test cases without asking?
No. The pattern is ask, review, approve. The agent reports what is affected and proposes updates; changes happen when you tell it to, and everything it does is scoped to your Jira permissions.
What if my links are incomplete?
Then the agent tells you that too: test cases that mention the feature but are not linked to the requirement are exactly the kind of gap it can surface, and linking them is one more sentence.
How is this better than a traceability matrix export?
The export is a snapshot that starts aging the moment it lands in a spreadsheet. The agent reads your live links at the moment you ask, and it reads the test case contents too, so it can say why something is affected instead of just that a link exists.
Ready to Get Complete
Testing Visibility?
Start using BesTest today and experience complete testing visibility from requirements to release. Free to get started!
Available on the Atlassian Marketplace. Install in seconds, free for up to 10 users.
Start Free on Marketplace