Java Cucumber E2E Automation
Budget: $8 – $15 USD
The core framework is already in place: Java 17, Selenium WebDriver and a containerised execution environment that spins up in Kubernetes through Skaffold. What I still need is a complete Cucumber layer that drives true end-to-end scenarios.
Scope of work
• Write Gherkin features that mirror our main user journeys (login, purchase flow, profile management and a couple of admin paths).
• Implement step definitions in Java, reusing existing WebDriver helpers.
• Make the suite run consistently in headless Chrome; the Docker image you build will be launched by Skaffold inside the cluster.
• Produce readable HTML/JSON reports and wire the exit codes so that they break the CI pipeline when a scenario fails.
• Document how to add new scenarios and how to invoke the tests locally through Skaffold or straight Maven commands.
Acceptance criteria
• All scenarios green in our staging namespace on Kubernetes.
• One-command execution: ‘skaffold run -p test’.
• Reports generated under /target/cucumber-reports with timestamps.
If you have previously wired Cucumber + Selenium inside Kubernetes or have solved the usual pod-to-browser display quirks, you’ll move very fast here. I can hand over the current repo, the Helm charts and the Skaffold yaml as soon as we agree on an approach.
Scope of work
• Write Gherkin features that mirror our main user journeys (login, purchase flow, profile management and a couple of admin paths).
• Implement step definitions in Java, reusing existing WebDriver helpers.
• Make the suite run consistently in headless Chrome; the Docker image you build will be launched by Skaffold inside the cluster.
• Produce readable HTML/JSON reports and wire the exit codes so that they break the CI pipeline when a scenario fails.
• Document how to add new scenarios and how to invoke the tests locally through Skaffold or straight Maven commands.
Acceptance criteria
• All scenarios green in our staging namespace on Kubernetes.
• One-command execution: ‘skaffold run -p test’.
• Reports generated under /target/cucumber-reports with timestamps.
If you have previously wired Cucumber + Selenium inside Kubernetes or have solved the usual pod-to-browser display quirks, you’ll move very fast here. I can hand over the current repo, the Helm charts and the Skaffold yaml as soon as we agree on an approach.