What it does
ReportPortal is a reporting and analysis layer for automated tests, not a test runner. A framework agent or reporting client sends results and metadata to an instance, where teams can inspect launches, logs, attachments, dashboards, and failure categories. It can be deployed as self-hosted software or used as a managed SaaS service, so it fits QA teams that already run tests and want a shared view of their outcomes.
Add the ReportPortal agent for the framework already used by a project, configure the instance URL, project, launch name, and access token, then run the suite through its existing runner or CI job. The agent sends test results and metadata; after a run, the launch view brings statuses, logs, attachments, and screenshots together for investigation. The documented client-library route is more manual because the project must implement reporting calls and metadata itself. No test suite or ReportPortal instance was used for this record.
Reporting is not execution
ReportPortal listens for framework events and visualizes results. Its integration guide explicitly says tests cannot be executed from ReportPortal, so it depends on a separate test runner and a reachable instance. Teams can use a managed SaaS instance or deploy the community version themselves. The Docker Compose guide lists a minimum of two CPU cores, 6 GB of Docker memory, and 20 GB of free storage, making the self-hosted option an infrastructure task as well as a reporting integration.
The project is Apache-2.0 licensed and the vendor describes a free self-hosted version. Managed SaaS plans include a 30-day trial and paid packages; the exact plan choice depends on instance type and data retention needs. The public trial/demo environment is shared, so do not treat it as a private destination for confidential test results.
Strengths
- Framework agents can send test results and metadata with limited integration logic, while a client library supports custom reporting.
- Launch reports group statuses with logs, screenshots, attachments, and historical test information.
- Automatic failure analysis and dashboards help teams triage recurring test issues.
Watch out for
- It does not run tests; a separate test runner or CI job must produce and send results.
- Self-hosting requires Docker Compose and at least the resources listed in the deployment guide.
- The shared demo is not appropriate for confidential test data.
Best for
- QA teams centralizing results from existing unit, functional, or integration test suites
- CI owners who need to inspect failures and trends across repeated launches
- Organizations prepared to integrate an agent or operate a self-hosted reporting instance
Sources
- What is ReportPortal? | ReportPortal Documentation (Oct 25, 2026)
- Test Framework Integration | ReportPortal Documentation (Oct 25, 2026)
- Deploy with Docker | ReportPortal Documentation (Oct 25, 2026)
- Pricing: SaaS | ReportPortal (Oct 25, 2026)
- LICENSE | reportportal/reportportal (Oct 25, 2026)
- FAQ | ReportPortal Documentation (Oct 25, 2026)
- ReportPortal test automation analytics platform and real-time reporting (Oct 25, 2026)