
When manual and automated tests are managed separately, teams retest work that automation has already covered and lose sight of what was actually verified. This guide explains how to combine manual and automated testing in Jira so both report against the same test cases, steps and results.
Manual testing is often laborious and time-consuming, and not always effective at finding certain classes of defects. Test automation can run those tests quickly and repeatedly, which makes it a cost-effective way to protect software quality over a long maintenance life. Yet tests are frequently automated with little visibility, so teams end up retesting manually because nobody can see what the automation covered.
Even organisations with mature automation spend significant time investigating automated test logs. The cause is usually a disconnect between the original manual test case design and what the automated test actually verified.
The problem grows when there are two or more separate testing teams:
Automation should not change your standards for test execution and reporting. Nobody should feel automation is a mysterious process because they cannot see confirmed coverage against the steps the test analyst designed.
The recommended approach is to manage automated tests in the same platform the rest of the project team uses for manual testing, such as Atlassian Jira. When you package a set of test cases, for example your regression suite, both the manual testers and the automation solution execute and report from the same suite in your test management system.
As automated coverage grows, manual effort should reduce towards your intended automation target. That frees the testing team to focus on results and on the tests and issues that have not been automated.
The aim is readable test scripts that both manual testers and automation engineers can manage and support. With Vansah Test Management for Jira, the workflow looks like this:
For implementation detail, see the Vansah API framework tutorial and API documentation. Our guide on integrating automated test results into Jira covers the wider pipeline setup.
A combined approach is working when the whole team trusts a single view of testing.
Check that your team has:
Testpoint’s test automation services help teams build frameworks that connect to Jira test management, so automation adds visible, trusted coverage rather than a separate stream of results.
Tell us about your Jira setup, your automation tools and where results are getting lost between teams. We will help you design a combined approach your whole team can trust.
Book a consultation