EffortlessATF vs building your own Serenity BDD framework
Serenity BDD and Cucumber are free and open source, so why pay for a framework? Because the libraries are the easy part. This page compares building on Serenity yourself with starting from EffortlessATF.
What "from scratch" really involves
A pom.xml with Serenity, Cucumber, Selenium and REST Assured takes an afternoon. A framework a team can rely on takes much longer, because of everything around the libraries:
- configuration for environments, with secrets kept out of the code;
- a step library that's generic enough to reuse, rather than one step per test;
- locator management that survives UI changes;
- waits and assertions that don't flake in CI;
- parallel execution with isolated state;
- a CI pipeline that publishes reports;
- conventions documented well enough for new team members, and now for AI assistants too.
Most teams reach these patterns after a year of maintaining a suite, usually after rewriting the first version.
Side by side
| Build on Serenity yourself | EffortlessATF | |
|---|---|---|
| Time to first green run | Days to weeks | Minutes: clone and run one command |
| Underlying stack | Serenity BDD, Cucumber, Selenium, REST Assured | The same open-source stack, in your own repository |
| Generic UI and API steps | Write and maintain your own | Included, so most tests need no Java |
| Locators | Your choice of pattern | YAML files per page, with a capture step to record them from the live page |
| Waits | Your responsibility | Smart waits and retrying assertions throughout |
| Secrets and environments | Your responsibility | Property, then environment variable, then config file |
| CI | Write your own pipeline | GitHub Actions workflow included |
| AI-assisted test creation | Ad hoc prompting | A documented workflow with a fixed vocabulary, validation and review |
| Licence cost | Free, plus engineering time | One-off per tester: £119 for the first, less for each extra tester |
| Lock-in | None | None: it's standard Maven, Java and Gherkin in your repository |
The cost question
A framework built from scratch isn't free: it's paid for in engineering time, first to build it and then to fix the patterns that don't scale. Even a few days of an automation engineer's time costs more than a licence for a team of ten (£398), and the licence gives you working examples, conventions and an AI workflow that have already been through that process.
When building your own is the better choice
- You have experienced automation engineers and an existing suite with conventions you want to keep.
- You need a different language or runner, such as Python, JavaScript or TestNG.
- You want to learn Serenity internals deeply as a goal in itself.
If your team wants working tests this sprint, and testers who can contribute without writing Java, starting from EffortlessATF is quicker.
See what's included
Paste one of your manual test cases into the live demo and see the kind of scenario the framework produces.