How jardevson/meuframeworkweb works
Project Type & Purpose
• This is an automated UI testing framework written in Java, using:
• Selenium WebDriver for browser automation
• Cucumber (Gherkin) for BDD scenarios
• JUnit 5 as the test runner
• Maven as the build tool
• It integrates with CI (GitHub Actions & Azure Pipelines) and generates HTML reports via Cluecumber.
File Structure
• Top‐level artifacts:
• pom.xml – Maven build & dependency management
• .github/workflows/… & azure-pipelines.yml – CI pipelines
• src/test/java packages (Page Object Model + SRP):
• core – WebDriver setup & lifecycle (Browser.java, Driver.java)
• maps – element locators (e.g. HomeMap.java, RegisterMap.java)
• pages – high‐level page actions (e.g. HomePage.java)
• steps – Cucumber step definitions & hooks (Hooks.java)
• runner – Cucumber/JUnit entry points (RunnerTest.java) and report generation (GeraRelatorio.java)
• utils – property‐file loader (PropertiesUtils.java)
• src/test/resources:
• features/ – Gherkin scenarios (*.feature)
• *.properties – environment configs (dev, hom, uat)
Key Insights from README
• Emphasizes Page Object Model & Single Responsibility
• Running tests via Maven with -Denv= and -Dcucumber.filter.tags=
• Reports generated with cluecumber-report:reporting
Main Components & Their Relationships
A. CI/CD Layer (top)
• GitHub Actions workflows (agendado.yml, regressivo.yml)
• Azure Pipelines (azure-pipelines.yml)
–→ triggers Maven build & test execution
B. Build & Dependency Management
• Maven (pom.xml)
–→ resolves Selenium, Cucumber, JUnit, Cluecumber
C. Test Execution Engine
1. Gherkin Feature Files (*.feature)
–→ fed into the
2. Cucumber Runner (RunnerTest.java)
–→ invokes
3. Step Definitions (steps/*Steps.java)
– which call
4. Page Objects (pages/*.java)
– which wrap
5. Element Maps (maps/*.java)
– that use
6. Core WebDriver Manager (core/Driver.java)
– to instantiate & control
7. Browser Driver (ChromeDriver/GeckoDriver)
– controlling the
8. Browser Instance
– to drive the
9. Application Under Test (AUT)
D. Configuration & Utilities
• PropertiesUtils reads dev.properties, hom.properties, uat.properties
–→ provides URLs, credentials, timeouts to core & pages
E. Reporting
• Cluecumber plugin (cluecumber-report:reporting)
– generates HTML & JSON test reports
• Custom report generator (GeraRelatorio.java)
Patterns & Principles
• Page Object Model: separate maps (locators) from pages (actions)
• Single Responsibility: each package has one role (core, pages, maps, steps, runner)
• BDD: feature files drive implementation via step definitions
• Modular CI: distinct workflows for scheduled vs tagged runs