How shagun-mahajan-lab49/quantum-starter-kit works
Main Components
• Automation Test Code – This is the heart of the project located under “src/main/java” with two key packages:
• Pages (Page Object Models): Classes like ExpenseTrackerHomePage.java, ExpenseTrackerLoginPage.java, GooglePage.java.
• Steps (Cucumber Step Definitions): Files such as ExpenseTrackerSteps.java, GoogleStepDefs.java, and CommonStepsDefs.java that connect the feature files to the application actions.
• Feature Files – Under “src/main/resources/scenarios”, where Cucumber/Gherkin files (appium.feature, webSearch.feature, etc.) define the test scenarios.
• Configuration & Data Resources – This includes:
• “resources/application.properties” for basic project properties and credentials.
• Environment-specific config files under “resources/android” and “resources/ios” (e.g., env.properties and .loc locator files).
• TestNG config files in “resources/config” (like testng_appium.xml and testng_web.xml) that manage the test suites.
• Test data files (CSV, JSON, XLS) under “resources/data” and locator files (in “resources/common”) for UI identification.
• Log configuration files (log4j.properties, log4j2.properties, etc.)
• Build and CI/CD Integration:
• Maven’s pom.xml defines dependencies and build scripts.
• The .circleci directory for CI configuration confirms automated builds/integration.
• External Services:
• Integration with Perfecto Mobile’s cloud for executing tests on real devices and for reporting.
Out the Relationships & Interactions
• The TestNG XML configurations serve as the gateway to execution. They pick up scenarios from the “scenarios” directory and use parameters defined in the “application.properties” and environment config files for mobile/web test runs.
• During execution, the features written in plain English (Gherkin) pull in the corresponding step definitions (located in “steps”) that then interact with the Page Object Model classes (stored in “pages”) to perform tests.
• The resource layer (configuration files, object locators, test data) is loaded by both the test code and the QAF (Quality Automation Framework) library, providing a dynamic and configurable testing environment.
• The build process is handled by Maven and integrated within the CI pipeline (CircleCI), ensuring that every commit triggers a proper build and test run.
• Logging and reporting are managed via log4j configurations and Perfecto’s reporting dashboard, feeding back the execution results.
Architectural Patterns & Design Principles
• Separation of Concerns:
• There’s clear segregation between the test definitions (features), step definitions (logic that drives tests), and the page objects (UI mappings).
• Modularity:
• Different modules for web vs. mobile tests are evident in the different TestNG XML files and resource folders (android, ios).
• Configurability:
• The use of multiple property files and object repository (.loc) files reflects a design that favors externalizing configuration and enabling data-driven tests.
• Integration of CI/CD: