Practice Exercises

Time to build. These exercises take you from zero to a fully configured Maven project that's ready for CI/CD. Do them in order — each one builds on the previous.

Exercise 1: Create a Maven Project from Scratch

1. Open IntelliJ > File > New > Project > Maven Archetype > maven-archetype-quickstart
2. Set groupId to com.testerrank and artifactId to banking-automation
3. Replace the generated pom.xml with the complete pom.xml from the POM Anatomy lesson
4. Create the folder structure: src/test/java/com/testerrank/base/, pages/, tests/, listeners/
5. Create a simple BaseTest.java with @BeforeMethod that reads browser from System.getProperty()
6. Create LoginTest.java with one @Test method that opens the TesterRank Banking Portal
7. Run mvn clean test from the terminal — verify the test executes

Exercise 2: Set Up Multiple Test Suites

1. Create testng-smoke.xml in src/test/resources — include only LoginTest
2. Create testng-regression.xml in src/test/resources — include all test classes
3. Run: mvn clean test -DsuiteXmlFile=src/test/resources/testng-smoke.xml
4. Run: mvn clean test -DsuiteXmlFile=src/test/resources/testng-regression.xml
5. Verify different numbers of tests execute for each suite

Exercise 3: Configure Profiles

1. Add browser profiles (chrome, firefox) to pom.xml
2. Add environment profiles (local, staging) to pom.xml
3. Add suite profiles (smoke, regression) that set suiteXmlFile property
4. Test: mvn clean test -Pchrome — should use Chrome
5. Test: mvn clean test -Pfirefox,smoke — should use Firefox with smoke suite
6. Run mvn help:active-profiles to verify which profiles are active

Exercise 4: Debug a Broken Build

1. Intentionally change a dependency version to something that doesn't exist. Run mvn clean test. Read the error message carefully.
2. Fix the version. Now intentionally put a test class in src/main/java instead of src/test/java. Run mvn clean test. What happens?
3. Move it back. Now rename your test class to LoginScenarios.java (doesn't end with Test). Run mvn test. How many tests run?
4. Run mvn dependency:tree and study the output. Find all transitive dependencies of Selenium.
5. Run mvn versions:display-dependency-updates to see if any of your libraries have newer versions.

Exercise 5: Prepare for CI

# Simulate what Jenkins would run:

# Step 1: Clone the repo (you already have it)
# Step 2: Run smoke tests headlessly
mvn clean test -Pchrome,smoke -Dheadless=true

# Step 3: Check the reports
ls target/surefire-reports/

# Step 4: Run regression tests
mvn clean test -Pchrome,regression -Dheadless=true

# Step 5: If all pass, you're CI-ready