We're excited to introduce the latest release of TestMonitor, version 8.1! This update delivers powerful new integrations for test automation along with several smaller improvements and performance enhancements. The outcome? Faster insights, cleaner collaboration, and fewer late-night scrambles to make sense of test output.
Let's explore what's new in this release.
Managing automation results has traditionally meant juggling multiple tools, including CI/CD logs, spreadsheets, and one-off dashboards. It’s time-consuming, error-prone, and often leaves gaps between automated and manual test reporting.
TestMonitor 8.1 makes those gaps easier to close. By connecting the TestMonitor CLI directly to your CI/CD pipeline—including GitHub, GitLab, or CircleCI—you can feed automation results straight into your test management hub.
Once results are in, they sit alongside your manual runs, all in one place:
Instead of bouncing between reports, teams get a single, reliable source of truth. Test leads can quickly see what broke, testers know which cases to rerun, and managers can review progress without waiting for another status update.
JUnit XML is one of the most widely adopted formats for sharing automated test results. Many of the tools you already use—like Cucumber, Robot Framework, or JUnit—produce it by default. The challenge comes later: Teams often shuffle those files around manually, reformatting them or copying failure notes into spreadsheets. That slows down triage and risks missing important details.
With TestMonitor 8.1, importing JUnit XML takes only a few steps:
From there, TestMonitor automatically extracts the test cases and their results.
Within moments, they appear in your project dashboard—complete with status and failure messages. Instead of wading through raw XML or scattered reports, your team gets instant insight into what passed, what failed, and why.
That means less time reformatting and more time acting on the results.
Playwright has become a go-to framework for end-to-end testing—it's fast, reliable, and designed for modern web applications. But for most teams, the challenge is sharing the results beyond development. Too often, that means writing custom scripts or pulling together ad hoc reports just to make the data useful for others. And crucial artifacts like screenshots get lost in the shuffle.
TestMonitor 8.1 adds native support for Playwright, removing that extra work. With the built-in reporter, your results—and all the vital evidence you need—flow directly into your project without manual formatting. This is especially useful for a feature like a sign-up form, where a successful run can be validated with a screenshot of the confirmation page, or a failed run with an image of an error message. Teams can review failures with supporting visuals, making issues faster to reproduce and easier to resolve.
Here’s how it works:
The reporter automatically uploads your Playwright cases and results—screenshots, screen recordings, and trace files included. Each outcome is displayed in TestMonitor alongside your manual and automated tests, giving everyone a single, centralized view. Teams can review failures with supporting visuals, making issues faster to reproduce and easier to resolve.
Selenium is the backbone of browser automation.
Most quality assurance (QA) professionals know it well: Write scripts that mimic user actions, run them across browsers, and verify that critical paths don’t break.
The challenge comes afterward. Raw logs stack up, screenshots land in folders, and context gets buried, making it difficult to connect results to the bigger testing picture.
TestMonitor 8.1 includes native support for Selenium, powered by a new TestNG listener that ties directly into your project. Instead of exporting results manually, TestMonitor collects and organizes them automatically.
Here’s how it works:
The listener uploads each test case and its result automatically, screenshots included. Developers no longer need to package logs, testers avoid re-running steps that have already passed, and managers get browser-specific issues in a clear, centralized view.
Reporting becomes consistent, context is preserved, and the whole team stays aligned.
Once test results are integrated, the next challenge is seeing the bigger picture.
Which tests are consuming the most time?
Where are the repeat failures?
How much of your testing is automated versus manual?
These questions often require hours of manual reporting—or worse, gut instinct.
TestMonitor 8.1 introduces a dedicated automation report designed to surface those insights directly. The report makes it simple to:
Instead of piecing together spreadsheets and dashboards, QA managers can now open a single report and know exactly where attention is needed. Teams save time, risks are easier to spot, and testing efforts become more predictable and measurable.
Clear documentation and focused review are what keep teams aligned.
That’s why TestMonitor 8.1 makes two practical improvements designed to cut down wasted effort and sharpen collaboration.
Writing up issues or results should be quick but clear. The updated editor now supports:
With these small but powerful additions, testers can capture exactly what happened without workarounds, and managers can scan reports for key details without digging.
Not all outcomes require equal attention, and sorting through them one by one is tedious.
The new filters let you:
The result is faster triage and fewer distractions, so teams can instead spend time solving the issues that block progress.
TestMonitor 8.1 extends the platform’s mission to make testing more organized, collaborative, and actionable. From integrating automation pipelines to sharpening reporting and documentation, these updates target the friction points QA teams encounter every day.
You can explore the full release notes for a detailed breakdown, or watch our video walkthrough to see the new features in action.
If you’re new to TestMonitor, now is the time to start. Begin your free trial and bring every part of your testing—manual and automated—into one clear, powerful hub.