ReportPortal screenshot thumbnail

ReportPortal

After every CI run, ReportPortal gathers test results from all of a team's frameworks into one dashboard, sorts the failures by cause, and keeps the history for comparison. Results stream in as tests execute and appear as launches with pass and fail counts, defect totals, and durations, then open into suites, tests, and steps with logs, stack traces, and screenshots. Failures are filed as Product Bug, Automation Bug, System Issue, No Defect, or To Investigate, and projects can define their own subtypes. Auto-Analysis uses machine learning to set the defect type, comment, and bug tracker link of a new failure from similar failures a person already investigated. Pattern Analysis flags known errors with string or regex rules, and Unique Error Analysis groups failed tests that share an identical error. Widgets for launch statistics, failure trends, flaky tests, and passing rates sit on dashboards, and saved filters narrow launches by name, attributes, or start time. Agents for Java, Python, JavaScript, and .NET frameworks report from any CI pipeline, and JUnit or Robot Framework result files import through the UI or API. Plugins link failures to Jira, Rally, Azure DevOps, GitLab, or monday tickets, notify Slack, Telegram, or email, and add LDAP, Active Directory, GitHub, or SAML sign-in. QA engineers triage nightly regressions, developers read failed-step traces, and release managers check pass rates. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy