A Java library for writing cleaner automated acceptance tests with rich living documentation and integration with Selenium, Playwright, and BDD tools.
Serenity BDD is a Java library designed to make writing automated acceptance tests easier and more structured. It helps teams create maintainable tests that integrate with tools like Selenium, Playwright, and Cucumber, while generating rich, living documentation that reflects both test outcomes and project requirements.
Test automation engineers, QA teams, and developers working on Java-based projects who need to write and maintain automated acceptance tests with clear reporting and integration with BDD tools.
Developers choose Serenity BDD for its ability to produce comprehensive living documentation from tests, its support for modern test design patterns like Screenplay, and its seamless integration with a wide range of testing frameworks and drivers.
Serenity BDD is a test automation library designed to make writing automated acceptance tests easier, and more fun.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates business-readable reports with test outcomes, requirements status, and step-by-step execution details, as showcased in the README's dashboard and requirements summary screenshots.
Supports Lean Page Objects, Action Classes, and the Screenplay Pattern for cleaner, maintainable test code, with the README linking to articles and courses on these approaches.
Seamlessly works with Selenium WebDriver, Playwright, RestAssured, Cucumber, and JUnit, evidenced by extensive compatibility tables and starter projects in the README.
Aggregates test results to reflect the status of requirements, features, and stories, providing clear project insights through detailed reports as shown in the README examples.
The Jira integration modules are deprecated and no longer actively maintained due to API restrictions, limiting native reporting for teams reliant on Jira.
Most development and bug fixes are prioritized for commercial support clients, as stated in the README, which can slow issue resolution for non-paying users.
Major versions like 5.0.0 introduced breaking changes requiring migration efforts, as noted in the release notes, potentially disrupting existing test suites.