Skip to main content

FAQ

On this page, we have put together a list of the most frequently asked questions. Here, you can find prompt responses.

  1. Does on-prem installed ReportPortal make any external calls? What are the content and nature of these calls?
  2. Assuming ReportPortal locally caches logs to understand their content, where are these stored, and what are the associated retention policies?
  3. How is data encrypted in transit and at rest?
  4. Does the containerized solution function as a standalone, or can it be integrated with K8S or other orchestration platforms? Is there a helm chart available?
  5. Is there any training available to use ReportPortal effectively?
  6. Is there a demo available?
  7. How can I begin using ReportPortal?
  8. Does the tool integrate with my existing test automation framework?
  9. What type of license does ReportPortal use?
  10. Does ReportPortal have any paid features?
  11. Does ReportPortal use AI?
  12. Do we need specific infrastructure prerequisites to avoid performance problems?
  13. What types of reports can I generate with the ReportPortal?
  14. Can ReportPortal aggregate performance test results?
  15. Does ReportPortal have integration with Jira?
  16. How can I check the ReportPortal version?
  17. How can I check if the ReportPortal API is working?
  18. What are the application limits in ReportPortal?

1. Does on-prem installed ReportPortal make any external calls? What are the content and nature of these calls?​

All test results and testing data reside in-house, within your instance of ReportPortal. However, there are two types of external calls that ReportPortal makes. The first checks our status page for the latest version and informs users of it on the login page. The second sends anonymized data to Google Analytics, helping us refine the user experience and better understand application usage. This can be toggled off if desired.

2. Assuming ReportPortal locally caches logs to understand their content, where are these stored, and what are the associated retention policies?​

ReportPortal utilizes PostgreSQL for its database, MinIO and the local system for file storage, and OpenSearch for log indexing and ML processes.

Retention policies can be set and adjusted within the application on a per-project basis.

3. How is data encrypted in transit and at rest?​

We use encryption in transit via SSL for our SaaS instances. For on-prem installation it depends on your LoadBalancer.

We use encryption at rest for our SaaS instances. It is provided by AWS and configured during VM provisioning. For on-prem installation it depends on your DevOps.

4. Does the containerized solution function as a standalone, or can it be integrated with K8S or other orchestration platforms? Is there a helm chart available?​

ReportPortal is containerized and can be orchestrated using either docker-compose or Kubernetes.

5. Is there any training available to use ReportPortal effectively?​

Check our Tutorial and read blog post with tips to get ReportPortal benefits. We also recommend investigate our documentation where you can find screenshots and video instructions on ReportPortal functionality.

6. Is there a demo available?​

You can explore ReportPortal without installation by visiting our demo instance which offers:

  • Free trial available indefinitely
  • Data is flushed every 24 hours
  • All enterprise features included

You can either join a shared project or create a personal one.

When a user visits the demo instance, they can log in using the default/pre-filled credentials. In this case, they will access a shared project that is available to everyone using the same demo account. This means that anything they report will be visible to all users and can be modified or managed by anyone.

Alternatively, the user can log in via GitHub. In this case, a personal project and user account will be created just for them. Only that user will be able to view and manage the data reported within their personal project.

If you need a personalized demo session, please leave your contact details. To get a quick overview, check out our demo video.

7. How can I begin using ReportPortal?​

The initial steps involve installing and configuring the tool. Installation steps you can find in our documentation.

8. Does the tool integrate with my existing test automation framework?​

ReportPortal can be integrated with common testing frameworks and CI tools. Consult this section of the documentation for detailed information on test framework integration. And use following links for Integration with CI/CD: Integration with GitLab CI, Integration with Jenkins.

9. What type of license does ReportPortal use?​

ReportPortal is licensed under Apache v2.0, which means it’s free to use, comes with no liability and warranty, and there is no service and support included. And can be utilized even for commercial usage.

10. Does ReportPortal have any paid features?​

We offer two premium features:

  • Quality Gates – a set of predefined criteria that must be met for a test run to be considered successful.
  • SCIM Server – helps automate user management by syncing users and their access rights between your identity provider and ReportPortal.

11. Does ReportPortal use AI?​

We provide ML-driven failure triage. Read this article to know how we use AI.

12. Do we need specific infrastructure prerequisites to avoid performance problems?​

Look into Hardware Requirements.

13. What types of reports can I generate with the ReportPortal?​

ReportPortal has a lot of widgets to visualize test results and understand the state of the product. Most popular our widgets: Overall statistics chart, Launch statistics chart, Failed cases trend chart, Launch execution and issue statistic, Component health check.

Depending on your needs, you can create either a report for a single test run or a Build/Release/Sprint Report. ReportPortal also allows you to generate various types of test automation reports using widgets, including:

  • Summary Report
  • Detailed Test Case Report
  • Trend Analysis Report
  • Failure Analysis Report
  • Execution History Report

14. Can ReportPortal aggregate performance test results?​

We do not support direct integration with performance testing frameworks, but as a workaround you can import performance test results in JUnit format into ReportPortal.

15. Does ReportPortal have integration with Jira?​

Our test automation reporting dashboard have integration with following Bug Tracking Systems: Jira Server, Jira Cloud, Azure DevOps, GitLab, Monday and Rally.

16. How can I check the ReportPortal version?​

You can find the current version of ReportPortal on the login page. Simply hover your mouse over the i icon next to the "New versions are available" message to see the version details.

17. How can I check if the ReportPortal API is working?​

Open your browser and go to the following URL: http://{your-hostname}/composite/info. This page provides essential information about the API's status.

18. What are the application limits in ReportPortal?​

ReportPortal has defined application limits to maintain stable performance and consistent API behavior across all projects and endpoints. Below is the complete list of limits and recommendations:

1. Pagination & Collections

Max page size: 300 items per page across collection endpoints:

  • Launches
  • Dashboards
  • Filters
  • Project members
  • Suites / Tests / Steps / Logs
  • Widgets

2. Dashboards & Widgets

  • Dashboards per project: up to 3,000 (increased from 300 in version 24.2).
  • Dashboard name length: 3–55 characters, must be unique per user per project.
  • Widget fullscreen auto-refresh: occurs every 30 seconds.
  • Test Case Search widget results cap: 300 total cases (10 per page × 30 pages).

3. Attributes & Text Fields

  • Attribute key length: up to 512 characters.
  • Attribute value length: up to 512 characters.
  • Quality Gate name length (Managed Plugin): 1–55 characters.

4. Files, Uploads & Storage

  • API attachment uploads: default limit 64 MB (configurable at the service-api level).
  • JUnit/Robot imports via UI: up to 32 MB per ZIP/XML file.
  • User avatars:
    • Accepted formats: JPEG, PNG, GIF
    • Maximum size: 1 MB
    • Maximum dimensions: 300×500 px
  • RabbitMQ message size: infrastructure-dependent; it’s recommended to keep log payloads reasonably sized, as very large logs may be rejected to process.

5. API Behavior & Miscellaneous

  • Rate limiting: none built-in; throughput and concurrency depend on infrastructure capacity.
  • Import timeout UX: works similar to /v2 reporting, depends on infrastructure.

6. Launch Merge

  • No hard cap, but treat around 20 launches per merge as a safe operational limit, unless you have tested higher based on your infrastructure size and data distribution.