Why TestNG structures test execution in Selenium Java - Framework Benefits

Framework Mode - Why TestNG structures test execution

Folder Structure

selenium-testng-project/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/
│   │           └── pages/
│   │               └── LoginPage.java
│   └── test/
│       └── java/
│           └── com/example/tests/
│               ├── LoginTest.java
│               └── BaseTest.java
├── testng.xml
├── pom.xml
└── README.md

Test Framework Layers

• Test Layer: Contains test classes like LoginTest.java where TestNG annotations (@Test, @BeforeMethod) define test methods and execution order.
• Page Object Layer: Classes representing UI pages (e.g., LoginPage.java) encapsulate web element locators and actions.
• Base Test Layer: BaseTest.java sets up WebDriver, configures browser, and manages test lifecycle with TestNG annotations.
• Configuration Layer: testng.xml controls test suites, groups, parallel execution, and test order.
• Utilities Layer: Helper classes for waits, logging, and reusable methods.

Configuration Patterns

testng.xml is the main configuration file. It defines:

• Which test classes or methods to run.
• Test groups for selective execution.
• Parallel execution settings (methods, classes, tests).
• Test dependencies and execution order.

Environment variables and browser settings are usually managed in BaseTest.java or external property files loaded during setup.

Test Reporting and CI/CD Integration

• TestNG generates default HTML and XML reports after test execution.
• Reports show passed, failed, skipped tests with stack traces.
• Reports can be integrated with CI/CD tools like Jenkins to visualize test results.
• TestNG listeners (e.g., ITestListener) can be implemented to customize reporting or trigger actions on test events.

Best Practices

• Use testng.xml to control test execution order and grouping instead of hardcoding in tests.
• Keep test methods independent; use TestNG dependencies only when necessary.
• Use annotations like @BeforeMethod and @AfterMethod for setup and cleanup to avoid flaky tests.
• Leverage parallel execution in testng.xml to speed up test runs but ensure thread safety.
• Implement Page Object Model to separate test logic from UI details.

Self Check

Where in this framework structure would you add a new test class for verifying the user registration page?

Key Result

TestNG structures test execution using annotations and XML configuration to control order, grouping, and parallelism.