Ask most QA teams where their tests live and you'll get two answers. The test cases live in a test management tool. The automated tests live in a code repository. Between the two sits a spreadsheet, a naming convention or a plugin that someone keeps in step by hand, until a test is renamed and the link quietly breaks.
Testver puts both in one place. Test Management in Testver is where you write test cases, plan and run them, and track defects, and every test case can be linked to the exact automated test in your repository that covers it. This post walks through how it works, from a requirement to a passing, linked, automated test.
What's in Testver Test Management
Test Cases: a library of manual test cases in folders, with steps, attachments and full version history.
Sources: the requirements, notes, documents and Jira issues your test cases come from.
AI Test Generation: drafts test cases from a source, or from your existing automation scripts.
Test Plans and cycles: group test cases for a release and run them, by hand step by step or automated.
Script Mapping: links each test case to the automated test that covers it, and flags when either side changes.
Coverage: traceability from requirement to test case to script to result.
Defects: raised from a failure in one click, tracked on a board, and pushed to Jira.
1. Write and organize test cases
Test Cases is your library. Each test case has a title, preconditions and numbered steps, and every step has an action, an expected result and optional test data. You classify each case by priority, type (Web, API, Mobile, E2E, Security, Accessibility and more), status, automation status and review status, and add tags and an estimated duration.
Folders group cases by feature, module or release, and counts roll up from sub-folders.
Filters narrow the list by priority, type, status, automation, review status, tags or the source a case came from.
Bulk actions move, tag, export or delete many cases at once.
Attachments keep screenshots, PDFs and documents with the case.
Version history: every edit creates a version. The History tab shows exactly what changed, field by field and step by step, and you can restore any earlier version.
Links point a case to its Jira issue, Confluence page, design or docs.
Export selected cases to Word, Excel or CSV when someone outside the team needs them.
Each case also shows its recent runs as coloured dots, so you can see at a glance whether it passed last time, and the Executions tab breaks every run down step by step.
2. Start from your requirements
Good test cases start from what the product is supposed to do. Sources is where you keep that material: requirement documents, free-text notes, other files such as PDFs and Word documents, and Jira issues. You can pull Jira issues in bulk with a JQL query, acceptance criteria included.
Every source shows how many test cases are linked to it. With one click, Create Plan bundles all of a source's test cases into a test plan that's ready to run. Sources feed AI Test Generation and coverage, and you can attach one to an AI Assistant chat, so the AI works from your real requirement instead of a guess.
3. Let AI draft the test cases
Writing test cases by hand is slow, and it's easy to miss the negative and edge cases. AI Test Generation does the first draft for you, in two ways:
From Sources: pick a requirement, note, document or Jira issue. The AI extracts each requirement from it, writes test cases for each one, then looks for gaps and fills them.
Reverse Engineer: pick existing automation scripts, and the AI writes the manual test cases they cover. It's the quickest way to bring an existing suite into test management.
Each generated case is labelled with the test-design technique behind it, such as happy path, negative, boundary, equivalence, error handling, security, accessibility or data validation, and with the user persona it tests as. Results stream in as they're written. You can group them by requirement, technique or priority, and a matrix shows which requirements each technique covers.
Turn on Use app knowledge and the AI grounds its steps in what Testver has actually seen of your application, so the steps use your real screens and fields. Each case is marked as grounded or not, and if your application behaves differently from the requirement, it flags possible spec drift. The requirement always decides what the test checks.
The AI also judges whether each case can be automated (automatable, needs setup or manual) and says why. You review the cases, save the ones you want into a folder, and each saved case stays linked to the source it came from. Incremental mode skips requirements that are already covered, so you can run generation again when a requirement changes without creating duplicates.
4. Plan and run your testing
Test Plans group test cases for a release or sprint. A plan holds references to your cases, not copies, so a fix to a case shows up everywhere it's used. Each round of testing is a cycle, with an owner, start and end dates, and an Overdue badge when it runs late.
Manual testing, step by step. Open a case in a cycle and you get its preconditions and steps in a table. Mark each step Pass, Fail, Block or Skip, write the actual result and a comment, and attach screenshots or logs as evidence. When a step fails, Create Defect opens a defect already filled in with the failed steps.
Automated tests in the same cycle. Test cases that are linked to a script show a bot icon. Click Run on one, or Run All Automated for the whole cycle, and Testver runs the real tests in your framework and writes the results back into the cycle automatically. You choose where they run (your own machine or a cloud provider), how many run in parallel, whether failed tests retry, and which environment and browser to use. With the Testver Grid add-on, you can watch the browser live as each test runs.
Every cycle keeps a live summary: passed, failed, blocked, skipped, not run, pass rate and completion. Re-run Failed creates a new cycle with only the cases that failed. Publish Results to JIRA posts the summary as a comment on the release's Jira issue.
5. Link every test case to its automation
This is the part most test management tools leave to you. Script Mapping links each test case to the automated test that covers it, down to the exact test in your repository. Select a test case, find the test among the scripts Testver discovered in your project, and click Map. One automated test can cover several test cases with Map Also.
A mapping isn't a note that goes stale. Testver watches both sides and tells you when they drift apart:
Synced: the case and the script match.
Case Updated: someone edited the test case, so the script may no longer match it.
Script Updated: the automated test changed since it was mapped.
Script Missing: the test was renamed or deleted.
A single Sync Health score shows how much of the map you can trust. The dashboard shows how many cases are mapped, how many aren't, and your automation coverage. When you've reviewed a change, Re-sync marks the mapping as trusted again.
And the AI writes the automation for you. On any manual test case, Automate with AI sends its steps to the AI Assistant, which writes the test in your own framework, following your project's conventions, runs it until it passes, and maps the new script back onto the case. From AI Test Generation, you can hand every automatable case to the AI Assistant in one go. Tests written by AI Record or the AI Assistant are filed as test cases and linked too, so your test management keeps up with your automation without anyone updating it by hand.
6. Traceability and coverage
Coverage brings it all together. Requirements are extracted from your sources, and each one is linked to the test cases that test it.
The Traceability Matrix shows each source with its requirement coverage, and opens into a heatmap of requirements against test-design techniques. You can see at a glance that login has happy-path and negative tests but no boundary tests.
The List View follows every requirement to its test cases and shows whether each one is fully, partially or not covered by automation, along with its latest result: passed, failed or not run.
Orphan detection finds test cases with no requirement, automated tests not linked to any case, and sources with no tests.
The Coverage Dashboard shows automation coverage by priority and by type, so you know where to automate next.
Export the matrix to Excel, or a single source to CSV, for a release sign-off or an audit.
Why it matters: a green test run on its own doesn't tell you what's covered. Linked test cases do. With Testver, "is this requirement tested, automated and passing?" has an answer you can show, without a spreadsheet.
7. Defects, from failure to Jira
When a test fails, you shouldn't have to copy the error into a bug report by hand. In Testver you can raise a defect from a failed automated run, a failed test in a cycle, or a failed manual step. It arrives filled in with the test name, file, browser, error and failed steps, and if that test already has a defect, Testver shows it instead of creating a second one.
Defects carry a severity, priority, steps to reproduce, environment, assignee, due date and attachments, and stay linked to their test case, so the case's run history shows the defect next to the failure. Track them on a board that you drag between columns (Open, In Progress, Resolved, Closed) or in a list grouped by severity. Push to JIRA creates the issue in Jira, and from then on Testver shows its live Jira status.
8. Moving from another tool
You don't have to start from scratch. Testver imports test cases from JSON and CSV files into the folder you choose. For an export from TestRail, Zephyr, Xray, PractiTest, qTest or another tool, attach the file to the AI Assistant and it maps the fields and imports the cases for you. Going the other way, you can export any folder, or all of them, to JSON or CSV. See Import and export.
Putting it together: one requirement, start to finish
Here's what a new feature looks like in Testver, end to end:
Add the requirement to Sources, or pull its Jira issue.
Generate test cases from it with AI Test Generation, review them, and save the good ones. They're linked to the requirement.
Automate the automatable ones with the AI Assistant. It writes and runs each test in your framework, and maps the script to its case.
Plan the release: click Create Plan on the source, or build a plan by hand.
Run the cycle: the automated cases run in one click, and the testers work through the manual ones step by step.
Raise defects from the failures and push them to Jira.
Check coverage in the Traceability Matrix: every requirement, its cases, whether they're automated, and whether they passed.
Later, when a developer changes the feature, Script Mapping flags the test cases whose scripts changed, so you know exactly what to review.
Free, and next to your code
Test Management is part of Testver, and Testver is free. It runs on your own computer or server, next to your test project, so your test cases, requirements and results stay with you. Your automated tests stay plain code in your own repository and framework, and keep working with or without Testver.
For the AI features, use Testver cloud AI, where you pay only for the AI you use, or a local model through Ollama or LM Studio, where the AI is free and nothing leaves your network. When the whole team needs one shared workspace, install Testver on an always-on server, or let us host it with Testver Cloud, an add-on. To see how Testver compares with separate test management and automation tools, read Why Testver is different.
Get started
Run testver serve in your test project, then follow the installation guide. Open Test Management and import the test cases you already have, or let AI Test Generation write them from your existing scripts. Then map them to your automation and watch your coverage fill in.