What problem does it solve?
This Skill empowers teams to adopt behavior-driven development by extending the e2e-tester workflow with Cucumber-based feature files, clear step definitions, and robust runners, reducing miscommunication between business, QA, and developers.
Core Features & Use Cases
- Feature file authoring & organization: Create and maintain Gherkin features and step definitions across Java (Cucumber-JVM) and JavaScript/TypeScript (Cucumber-JS), with Spring Boot integration where applicable.
- Runners & reporting: Integrate with Cucumber runners (JUnit Platform, JUnit 5) and generate human-friendly reports to verify end-to-end behavior.
- Multi-language support: Works with Java and JS ecosystems, enabling shared test strategies for UI (Playwright/Selenium) and API layers via the e2e-tester.
- Reusable steps & data tables: Promote modular, reusable steps, data tables, and scenario outlines for scalable test suites.
Quick Start
Add a sample feature file under src/test/resources/features, implement corresponding step definitions in Java or TypeScript, and execute tests using your project’s e2e-tester runner.