How vimukthi101/mbmc-selenium works
Main Components
• Automation Framework Core: Represented by the base classes (e.g., BasePage.java in the “com.qa.base” package and BaseTest.java in the tests section). These provide common functionality and setup/teardown logic.
• Page Objects: These are classes that directly interact with elements on the MBMC site. You have multiple page packages (e.g., “com.qa.pages” and “com.qa/pages/insurance”) that include pages like HomePage, LoginPage, and specialized pages such as PdwPage.
• Test Suites/Flows: Under “src/test/java/com/qa/tests” you see directories for “insuranceForm” and “pwdForm”. These contain tests for various scenarios – successful flows, inputs validation (invalid inputs, missing parameters, etc.). They also include test data classes.
• Supporting Resources: These include configuration and resource files (testng.xml and files in the target/resources directory), which support test execution parameters and data files.
• Build/Configuration: The Maven pom.xml file and the project’s directory structure support dependency management and project build processes.
Relationships and Component Interactions
• Maven build process (from pom.xml) as the component that orchestrates dependency injection, builds, and test runs.
• External test runner (via testng.xml) as a trigger that coordinates the execution of test classes from the project.
Architectural Patterns and Design Principles
• That the Page Object Model (POM) is reflected in the separation between page classes (domain-specific interactions) and test classes (workflow and scenario testing).
• That the project adheres to principles of modularity and reusability, as evidenced by the separation of insurance-related pages from other pages.
Relevant Technologies and Frameworks
• Selenium for browser automation.
• TestNG (as indicated by testng.xml) which manages test execution.
• Maven for build management.
• Java as the programming language.
Essential Elements
• Clear labels for each component (e.g., “BasePage”, “LoginPage”, etc.).
• A section that indicates external resources (MBMC site being automated) and external frameworks (Selenium, TestNG, Maven).
• Use annotations where necessary to highlight how test data (TestData in tests) supports the flow of test execution.