Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Batch reporting of test results #1970

Open
aleksanderpaliszewski opened this issue Apr 12, 2024 · 1 comment
Open

Batch reporting of test results #1970

aleksanderpaliszewski opened this issue Apr 12, 2024 · 1 comment

Comments

@aleksanderpaliszewski
Copy link

Issue:
Currently, the process of reporting test results to Report Portal involves sending individual HTTP requests for each test item, leading to potential performance bottlenecks, especially in scenarios with a large number of tests. This approach can strain the server and even lead to server overload, resembling a distributed denial-of-service (DDoS) attack.
https://reportportal.io/docs/dev-guides/ReportingDevelopersGuide#preconditions

Proposed Solution:
Implement batch reporting of test results, where multiple test items are aggregated and sent in a single HTTP request to Report Portal. This approach will significantly reduce the number of requests made to the server, thereby alleviating the load on the infrastructure and improving overall performance.

Question:
Is there a plan of implementing such a solution, or are there any blockers preventing its creation that we are not yet aware of? Otherwise, the infrastructure must be unnecessarily prepared for high peaks of requests in a short period.

@Kozovskaya
Copy link

Hello, @aleksanderpaliszewski
Thank you for your feature request, it’s a valid one. But implementing batch reporting requires updates both on api and clients’ side. Currently our team can’t address the issue due to road map priorities, but I will add your feature request to our Backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants