How yogesh2511/codingtestapexsystemslabcorp works
Project type and purpose
• This is a QA Automation Framework for LabCorp’s Careers site. It’s both a UI test suite (Selenium WebDriver + Page Object Model) and an API test suite (REST-Assured), orchestrated via Cucumber BDD and TestNG, packaged with Maven.
File structure
• Top-level directories:
• src/main/java/api/clients, api/models, api/services → HTTP client code + domain objects for API tests
• src/main/java/pages → Page Object classes for UI tests
• src/main/java/stepdefinitions → Glue code binding Gherkin steps to actions
• src/main/java/hooks → Cucumber hooks for setup/teardown (UIHooks, APIHooks, ScenarioHooks)
• src/main/java/utilities → Shared helpers (DriverManager, Config, FileUtils, LoggerUtils, WaitUtils, ExtentManager, etc.)
• src/main/resources/features → Gherkin feature files (UI & API)
• src/main/resources/config.properties, runner/testng.xml → configuration files
• Build & run: pom.xml, Maven lifecycle, TestNG runner (TestNgRunner).
Key insights from README
• Tech stack: Java 17, Maven, Selenium, REST-Assured, Cucumber BDD, TestNG, ExtentReports.
• Design pattern: Page Object Model.
• Reporting: ExtentReports and Cucumber HTML.
• Custom logging and screenshot capture on failures.
• ScenarioContextManager shares state across steps.
Main components
A. Feature Files (Gherkin)
B. Test Runner (TestNgRunner + Cucumber)
C. Step Definitions (UISteps, ApiSteps)
D. Hooks (UIHooks, APIHooks, ScenarioHooks)
E. Page Object Layer (ApplicationPage, HomePage, CareersPage, JobDetailsPage, etc.)
F. API Layer
1. Clients & Models (RestClient, Address, Customer, Order, Payment, Shipping, Response, etc.)
2. Services (OrderService)
G. Utilities
• DriverManager → WebDriver lifecycle
• Config → load config.properties
• FileUtils → read/write JSON payloads
• LoggerUtils → custom logging to Application.log, Selenium.log
• WaitUtils, WebElementHelper, JavaScriptUtils
• ExtentManager, ReportHelperListener → report generation
H. External Systems
1. Browser (Chrome via WebDriverManager)
2. LabCorp Careers Web Application (UI under test)
3. LabCorp API endpoints
I. Artifacts
• HTML Reports (ExtentReports, Cucumber Reports)
• Logs (.log files)
• Screenshots on failure
Relationships & data flow
1. Runner loads Feature Files → Cucumber kicks off Scenarios
2. Hooks initialize context:
• UIHooks → starts WebDriver via DriverManager
• APIHooks → configures RestAssured base URI
3. Step Definitions execute:
• UI steps call methods on Page Objects → Page Objects use WebElementHelper, WaitUtils → WebDriver → Browser → UI under test
• API steps call Services → Services use RestClient → HTTP request/response to API endpoints → ScenarioContextManager stores response data
4. Utilities invoked throughout for config, logging, file I/O
5. On each step or failure, LoggerUtils writes logs; UI failures trigger screenshots
6. After scenario, ReportHelperListener and ExtentManager collect test results → generate HTML reports
7. Hooks teardown: close browser, clear context
Architectural patterns & design principles
• Page Object Model for UI abstraction
• Service/Client separation for API (models vs. service logic)
• Cucumber BDD to keep tests readable and maintainable
• Hooks to centralize setup/teardown
• Utilities to avoid duplication and handle cross-cutting concerns (logging, waits, config)