Back to blog
Manual and automated testing in one place, finally
If you have been around ReportPortal for a while, you know the request we heard most often: give us a place for manual test cases, so we don't need to run a separate TMS on the side. That is exactly what is coming in the next ReportPortal release: a built-in Test Management System.
In practice it means you write and organize test cases, run them manually and track results in the same project where your automation already reports. One tool less to maintain, one login less to remember. And nobody has to ask where the test cases live anymore.
Why we built it
A typical QA team runs automation in one tool and manages manual test cases in another: a dedicated commercial TMS, a plugin on top of the bug tracker, sometimes still a spreadsheet. Each of these keeps its own piece of the truth. Before every release somebody spends half a day stitching those pieces into a picture of product quality. That work adds no value. It just burns hours and kills traceability along the way.
With TMS inside ReportPortal the stitching simply goes away. Everything is connected because it was never separated in the first place.
There is also a second reason, and for us it is the bigger one. Everyone right now is talking about Agentic QA and fully autonomous testing. We are too, and we spend a lot of time designing for it. But the deeper we went into agentic testing, the clearer it became: an agent needs an environment to live and work in. It needs structured test cases connected to real execution history. When the cases sit in one system and the results in another, there is nothing for an agent to stand on, no matter how good the tools are on their own.
That is how we arrived at test case management. A unique test case is the base value object of the whole system, the thing the rest of the magic builds on. It can be written by a manual tester, generated through LLM and MCP calls, or reported from your automation. Once it lives in the Library, plans, milestones, analytics and future agents can all work with it.
So treat this release as groundwork. We will keep adding functions step by step until a QA Agent has a complete environment to operate in. Don't judge the movie by its first frames. We have more to show.
What's inside
TMS consists of four modules. Together they cover the whole manual testing cycle:
1. Test Case Library
This is where your test cases live. Folders and subfolders, priorities from Critical to Low, custom tags. A case can be written as free text, which works fine for exploratory testing, or as steps with expected results when you need more structure.
A few things worth mentioning:
MCP for the Test Library: manage your test cases with your favorite AI tools.
Drag-and-drop folder and test case organization
Bulk operations: move, duplicate, retag, or reprioritize hundreds of cases at once
CSV import, if you are migrating from another tool
Audit history for every change
Search and filters across your Test Case Library
2. Test Plans
A test plan is a slice of the Library: the cases you need for a specific feature, release, or regression cycle. You can add attributes for filtering and duplicate a plan that worked before instead of building the next one from zero.
In practice, test plans connect the repository to actual execution. Coverage becomes a decision you make, not something that just happens.
3. Milestones
Milestones add the time dimension. Define a period (a sprint, a release, a feature, anything custom) and attach test plans to it.
Set start and deadline dates, track the status (Active, Completed and so on), and see how testing moves against the project timeline.
4. Manual Launches
This is where the actual work happens. Create a Manual Launch from a Test Plan, and the team gets a checklist with every case pre-loaded and grouped by folder.
During execution:
Mark tests as Passed, Failed, Skipped, or In Progress right from the execution page
Add comments and attach evidence
Link failures directly to your bug tracker (BTS integration)
A built-in timer shows how long each test actually takes
How it connects
The whole point is the chain:
Test Case Library → Test Plans → Milestones → Manual Launches → Results & Reporting
And all of it sits next to your automated test reports. QA leads see actual coverage instead of guessing. Engineers get a clear execution flow. Managers get their numbers without asking three people for three different exports.
What's next
We are not stopping here. Already in the works:
Organization-level views for teams managing multiple projects
Dashboards that show manual and automated results side by side
Traceability from requirements through test cases down to defects
ML-based analysis of quality trends across the whole test suite
We will share details on each of these closer to release. But one thing from the roadmap is the team's favorite, so it deserves a few words right now.
Automation that documents itself
This one is not in the current release, it is where we are heading. Picture the scenario: you integrate ReportPortal with your automation and just keep running it as usual. RP will document it for you, transforming launches into unique test cases inside the Test Case Library. Test documentation stops being something you write by hand and starts growing out of the tests you already run.
And even if you never plan to touch manual testing in RP, this will give you an honest view of what your automation covers and how it progresses, through the lens of milestones, environments and versions.
How to get it
Test Management will be available with ReportPortal 26.1. Once the release is out, simply update your instance and you'll find the TMS section in the project sidebar.
If you'd like an early look, have any questions, or are interested in seeing Test Management in action, get in touch to book a demo. During the session, you'll learn more about the new features, discuss your use cases, and explore ReportPortal plans and pricing options.
Not using ReportPortal yet? Request a free trial and poke around.
Be among the first to experience what's next
The next major ReportPortal release is coming soon. For us this is the biggest addition to ReportPortal in years: one platform for the full testing cycle, manual and automated together. ReportPortal is evolving from a test automation reporting solution into a unified QA Intelligence platform.
The upcoming release will introduce a new experience for managing testing activities across teams. In addition to Test Management, you'll also get access to powerful enterprise capabilities such as Organizations, along with many more enhancements.
Join the closed beta
Would you like to explore the new ReportPortal experience before the official release?
Complete the form to request access to our closed beta environment. Our team will contact selected participants and provide everything needed to start testing and share feedback.