How pavlinbg/ozonetests works
Main Components Identification
The project is a test automation framework with three distinct testing solutions. Here's how to represent the main architectural components:
A. Create three main container blocks representing the test solutions:
• Web Testing Suite
• API Testing Suite
• Mobile Testing Suite
Detailed Component Breakdown
For the Web Testing Suite (Most Complex):
• Test Layer (Tests folder)
• Page Objects Layer (Pages folder)
• Actions Layer (Actions folder)
• Base Layer (Base folder)
• Objects Layer (Objects folder)
• Properties Layer (Properties folder)
For the API Testing Suite:
• A simpler structure with:
• Test Cases
• API Endpoints
• Assertion Components
For the Mobile Testing Suite:
• Represent:
• Test Cases
• Mobile Screen Objects
• Mobile Actions
Technology Stack Integration
• NUnit (Testing Framework)
• Selenium WebDriver (Web Testing)
• RestSharp (API Testing)
• Appium (Mobile Testing)
Key Relationships to Highlight
• How Page Objects are used by Test classes
• Relationship between Actions and Pages
• Demonstrate how Base classes are inherited
• Property file usage across components
• Shared utilities and common patterns
Additional Elements
• Configuration management
• Test execution flow
• Reporting mechanism
• External dependencies (browsers, mobile devices, API endpoints)
Specific Implementation Details
For Web Testing:
• Hierarchy: BasePage → Specific Pages → Tests
• How OrderActions interact with Pages
• Relationship between User/Book objects and tests
For API Testing:
• Connection between APITests and assertion components
• API endpoint mapping
For Mobile Testing:
• Relationship between MobileAppScreen and test classes
• Device interaction flow