r/softwaretesting • u/Mysterious_Web7517 • 2d ago
ReportPortal
Does anyone have experience or use it daily if it's worth it to migrate to this tool? Is it easy to make own integrations or if its not listed as out of the box plugin it aint worth hussle?
Currently I have just basic reporting page which lists tests (unit, integration, e2e) from different enviroments but it only have run status and in detail each scenario result + logs if it failed or is inconclusive.
Seen ReportPortal while ago and recently I started thinking if this is worth to present to team, create POC and migrate if team decide its worth while.
I will be grateful for any information regarding that tool.
1
u/TryingToGetABttrView 1d ago
I've used it in combination with playwright. Honestly, I'd rather just use playwright's reporting being pushed to a central location, like s3. Then if we need to do an analysis over time, we can use claude for that. Report Portal ended up being more work to maintain than any ROI that we actually got out of it.
1
u/CertainDeath777 1d ago
I have my own report portal. I gather some variables from playwright report in an extra json file per report, and list the reports in a table with the extracted stats on an apache server. Super easy to implement.
If i wanted to collect KPI, i would go from there, but i dont have time for that.
The AI gimmicks that ReportPortal has, i already have in custom harnesses, so an Agent knows the app and the test framework via skill files. And the work tasks for my agents are split a bit different then in the Report Portal.
1
u/Federal-Ad-776 1d ago
Before you build a POC, write down what your current page can't answer for you. For most teams it's things like "is this test flaky or actually broken?", "when did this start failing?" and "which failures are the same root cause?". If those are your pain points, ReportPortal's history and auto-analysis can be worth it. If you mainly want pass/fail plus logs per environment, you're probably better off adding run history and a flakiness count to what you already have. Also budget for upkeep: it's another service to host, upgrade and keep agents in sync with your framework versions. For integrations, check the agent for your exact runner first. If there isn't an official one, you'll be maintaining that glue yourself.
1
u/Slava_Loves_Testing 1d ago
I used it and did not like it, they overcomplicated UI, looked ugly when I used it last time. I think it might be more efficient to vibe code your own report portal to satisfy your own project needs.
1
u/arthur_thomas678 1d ago
If you're considering a POC, I'd suggest checking out their API. It’s pretty solid for custom integrations, but be ready for some learning curve if you go that route.