annajsbecker
New member
Hi everyone,
I’m currently setting up the E2E automated testing architecture for a web application project, and I'd love to hear how other teams handle test execution reporting and living documentation.
We are using Java and Selenium with Cucumber BDD. While running tests in CI/CD works fine, our main challenge is sharing readable execution reports with non-technical stakeholders (Product Managers, BAs) without manually converting XML/JSON logs after every build.
We're considering implementing serenity bdd to generate out-of-the-box aggregate reports and map scenarios to user stories, but I'm curious about real-world experiences:
I’m currently setting up the E2E automated testing architecture for a web application project, and I'd love to hear how other teams handle test execution reporting and living documentation.
We are using Java and Selenium with Cucumber BDD. While running tests in CI/CD works fine, our main challenge is sharing readable execution reports with non-technical stakeholders (Product Managers, BAs) without manually converting XML/JSON logs after every build.
We're considering implementing serenity bdd to generate out-of-the-box aggregate reports and map scenarios to user stories, but I'm curious about real-world experiences:
- What tools/frameworks do you use to present test execution results to business users?
- How do you manage test reporting performance as your scenario suite scales into hundreds of tests?
- Do you prefer standalone reporting wrappers or integrating directly with test management dashboards?