How unxusr/elmenus works
Main Components
a) Test Framework Layer
• Behave Framework (Top-level orchestrator)
• Feature Files Container
• Step Definitions Container
• Environment Configuration
b) Page Object Model Layer
• Base Page Component
• Specific Page Objects
• E2E Objects
c) WebDriver Layer
• Browser Drivers (Chrome/Firefox)
• Selenium WebDriver
d) Reporting Layer
• Allure Reports Generator
• Screenshots Storage
• Logs Management
Component Relationships
[Feature Files] → [Step Definitions] → [Page Objects] → [WebDriver] → [Browser]
• ↘ [Reports & Logs]
Specific Implementation Details
• Feature files location (/features/test_scenarios/)
• Step definitions (/features/steps/)
• Page Objects (/features/pages/)
• Configuration files (behave.ini)
• Report output directory (/reports/)
• Screenshot storage (/failed_scenarios_screenshots/)
Important Elements to Highlight
a) Test Structure:
• Three main feature files (e2e_scenario, sign_in, sign_up)
• Their connection to corresponding step definition files
b) Page Object Pattern:
• Demonstrate inheritance from base_page.py
• Relationship between page objects and step definitions
c) Reporting Flow:
• How test execution results flow to the reporting system
• Screenshot capture mechanism for failed tests
[Test Scenarios] → [Step Definitions] → [Page Objects] → [Base Page]
• ↓
• [WebDriver Interface]
• ↓
• [Browser Instance]
• ↓
• [Target Website]