Log data in ReportPortal
ReportPortal is a CI/CD agnostic tool. Therefore, you can continue using your favorite CI/CD tool (GitLab, Jenkins, GitHub, Azure DevOps, Bamboo) to send data to ReportPortal and get test results of execution.
The data transmission is regulated not by the CI/CD process, but by the test framework. The only requirement is to ensure that the machine where your CI/CD is located has access to the ReportPortal instance to which you are trying to send the data.
As for test frameworks, a generic approach is to set the address of ReportPortal and other data in your test framework via properties or a configuration file, and your test framework will start reporting data to ReportPortal.
ReportPortal supports various frameworks. For example, we have integration with Java frameworks (TestNG, Jbehave, etc.), Python frameworks (Pytest, Robot Framework, etc.), JavaScript frameworks (Playwright, Postman, etc.), .NET frameworks (NUnit, VSTest, etc.).
Integration with ReportPortal is not dependent on the type of tests you run. It can be API tests, integration tests, or UI tests such as Selenium, Cypress, so, you can run different types of tests and get test results.
ReportPortal can be integrated with external services, enabling you to report test results from platforms like Browserstack, Sauce Labs, and other third-party services. For Sauce Labs integration, we have a plugin.
📄️ Implement own integration
You can find a detailed description of how report results to ReportPortal in our developers` guide.
📄️ Reporting SDK
How to report tests with nested steps?
📄️ Import data to ReportPortal
Import via UI
📄️ How to get an access token in ReportPortal
There are two ways to authorize in the ReportPortal API:
📄️ How to report attributes to ReportPortal
Attributes are essential for categorizing, filtering, and analyzing test data. This article will guide you through the process of reporting attributes to our test results reporting service.
📄️ How to run your tests
Automated tests can be executed in the any CI tool you are using on the project (Jenkins, Bamboo, Azure DevOps, GitHub Actions, CircleCI, TeamCity, GitLab, Travis CI, Codeship, Buddy, GoCD, Wercker and more).
🗃️ Test Framework Integration
6 items