SaveLink adds a requirements registry, branch comparison and run planning to SaveTest

SaveLink has released an update to SaveTest, its test management platform. The announcement was published on 8 October 2026 and names three key features: a requirements registry with a traceability matrix, branch comparison, and test run planning. The available part of the material contains no performance metrics, customer numbers or pricing, so the release can only be judged by its feature set and by which QA team tasks it addresses.

What's in the release

The main change is the link between requirements and tests. Until now, such systems mostly stored test cases and run results, while requirements lived in an issue tracker or in documents. Now the requirements registry sits inside SaveTest, and the matrix shows which requirements are covered by tests and which have no verification.

The update consists of the following, according to the stated description:

• a requirements registry inside the platform;
• a traceability matrix linking a requirement, a test case and a result;
• branch comparison;
• test run planning;
• announcement date: 8 October 2026, source: CNews.

Why traceability matters

The traceability matrix answers the question QA leads hear before every release: what exactly did we test, and what remains uncovered? If a requirement is linked to test cases and their latest results, a gap is visible immediately, with no manual cross-checking of spreadsheets. This transparency matters most for projects with audits, regulatory requirements or a long product life cycle: it lets teams show auditors how each requirement is proven by a test.

There is also a reverse effect. Test cases with no link to a requirement are easy to spot. They stay in the suite out of habit and eat up run time without protecting anything specific.

Branches and planning

Branch comparison addresses the problem of parallel development. When a product evolves along several lines, for example a main branch, a release branch and a branch for a large feature, the test suites drift apart. A comparison tool lets teams see how the versions differ and avoid losing changes during a merge. Implementation details are not disclosed in the available excerpt: it is unclear whether only test cases are compared, or requirements and results as well.

Run planning is a more down-to-earth feature, but it is the one that shapes day-to-day work. Run schedules, the assignment of tests to people and builds, visibility into team workload: all of this usually lives in spreadsheets and chats. Moving it into the platform reduces the chance that a regression run gets forgotten or launched on the wrong build.

Market and context

SaveTest enters a crowded market. TestRail, Qase, Allure TestOps and Test IT are already there, and each has its own version of traceability and planning. SaveTest will therefore have to stand out on integration depth and on how convenient its branch handling is. Against the backdrop of widespread AI adoption in testing, for example generating test cases from requirements, something else stands out: the available part of the announcement says nothing about AI features. The release is about process and discipline, not automatic generation.

What to check before adopting

Teams considering the update should ask the vendor a few questions:

• how requirements get into the registry: import from an issue tracker, API or manual entry;
• whether requirement statuses can be synchronized with tasks in Jira or similar tools;
• what exactly is compared when branches are matched and how conflicts are resolved;
• whether there are coverage reports suitable for audits;
• which deployment options are available: cloud or an on-premises environment.

For a pilot, it is enough to take one product with two active branches and measure how much time it takes to prepare a coverage report before and after the switch. If the matrix is built automatically and matches reality, the feature pays for itself. If the links have to be maintained by hand, there will be no gain.