How rohinegi548/cucumber-bdd-automation-framework works
Project type and purpose
• This is a Cucumber-BDD Selenium-based automation framework implemented in Java with Maven.
• Purpose: automate web UI tests using Feature files (Gherkin), step definitions, Page Object Model, and generate rich HTML reports (Cucumber reports + Allure).
File structure
• Top-level:
• pom.xml (Maven build & plugins)
• log4j.properties (logging)
• src/main/java/com/cucumberFramework – core code
– enums (Browsers, OS)
– helper (constants, logger, explicit waits)
– pageObjects (Page Object Model classes)
– stepdefinitions (Cucumber glue code + ServiceHooks for setup/teardown)
– testBase (TestBase: WebDriver setup & config)
– testRunner (TestRunner: Cucumber + TestNG runner)
• src/test/resources
– drivers (ChromeDriver binaries)
– features (Gherkin .feature files)
• Reports & outputs: target/ and test-output/ containing Cucumber-reports, allure JSON, advanced reports, TestNG/Surefire HTML.
• Execution Demo (video) & images folder for documentation.
README insights
• Describes the two sample scenarios (simple login + parameterized search).
• Lists Maven goals: mvn clean test, mvn site.
• Explains reporting plugins:
• net.masterthought:maven-cucumber-reporting
• ru.yandex.qatools.allure:cucumber-jvm-adaptor + allure-maven-plugin
• Mentions Jetty plugin for local hosting of Allure report.