Configuration management in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of Selenium WebDriver Configuration Code

What will be the output of the following Selenium WebDriver configuration code snippet when run?

Selenium Java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;

public class TestConfig {
    public static void main(String[] args) {
        System.setProperty("webdriver.chrome.driver", "/path/to/chromedriver");
        WebDriver driver = new ChromeDriver();
        driver.get("https://example.com");
        System.out.println(driver.getTitle());
        driver.quit();
    }
}

A Throws NoSuchSessionException when calling getTitle()

B Throws IllegalStateException due to missing driver executable path

C Prints an empty string and keeps the browser open

D Prints the title of the webpage 'Example Domain' and closes the browser

💡 Hint

Check if the driver path is set correctly and what getTitle() returns for https://example.com

The code sets the ChromeDriver path correctly, opens the browser, navigates to example.com, prints the page title 'Example Domain', and then closes the browser.

❓ assertion

intermediate

Valid Assertion for Configured Timeout in Selenium

Which assertion correctly verifies that the implicit wait timeout is set to 10 seconds in Selenium WebDriver Java?

Selenium Java

driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10));
Duration timeout = driver.manage().timeouts().getImplicitWaitTimeout();

A assertEquals(Duration.ofSeconds(10), timeout);

B assertTrue(timeout.toSeconds() > 10);

C assertNotNull(timeout);

D assertFalse(timeout.isZero());

💡 Hint

Check the exact value of the timeout Duration object.

The assertion must check that the timeout Duration equals exactly 10 seconds. Only option A does this precisely.

🔧 Debug

advanced

Identify the Configuration Bug in WebDriver Setup

Given the following Selenium WebDriver setup code, what is the cause of the runtime error?

Selenium Java

System.setProperty("webdriver.chrome.driver", "chromedriver.exe");
WebDriver driver = new ChromeDriver();
driver.get("https://example.com");

A The URL is invalid and causes MalformedURLException

B The driver path is relative and may not be found, causing IllegalStateException

C Missing call to driver.quit() causes memory leak error

D ChromeDriver constructor is deprecated and causes NoSuchMethodError

💡 Hint

Check how the driver executable path is specified.

Using a relative path without full absolute path can cause the driver executable not to be found, leading to IllegalStateException.

❓ framework

advanced

Best Practice for Managing Multiple Environment Configurations

In a Selenium Java test framework, which approach is best for managing different environment URLs (e.g., dev, staging, production) without changing code?

A Use a properties file for each environment and load the correct one based on a system property

B Hardcode all URLs in the test classes and comment/uncomment as needed

C Use environment variables only and avoid any config files

D Manually edit the URL in the test method before each run

💡 Hint

Think about maintainability and automation friendliness.

Using properties files per environment and selecting via system property allows easy switching without code changes and supports automation.

🧠 Conceptual

expert

Impact of Configuration Management on Test Reliability

How does proper configuration management improve the reliability of automated Selenium tests?

A By eliminating the need for assertions in test scripts

B By allowing tests to run faster through parallel execution only

C By ensuring consistent environment setup, reducing flaky tests caused by misconfiguration

D By automatically fixing bugs in the application under test

💡 Hint

Consider what causes flaky or unreliable tests in automation.

Proper configuration management ensures environments are consistent and stable, which reduces test failures caused by environment issues.

Practice

1. What is the main purpose of configuration management in Selenium Java testing?

easy

A. To separate test settings from test code for easier maintenance

B. To write test cases faster by skipping setup

C. To increase the number of test cases automatically

D. To reduce the number of test assertions

Solution

1. Step 1: Understand configuration management role

   It separates configuration data like URLs, credentials from the test logic.

2. Step 2: Benefits of separation

   This separation makes tests easier to maintain and adapt to different environments.

3. Final Answer:

   To separate test settings from test code for easier maintenance -> Option A

4. Quick Check:

   Configuration management = separation of settings and code [OK]

Hint: Think: settings outside code for easy updates [OK]

Common Mistakes:

• Confusing configuration management with test execution
• Thinking it speeds up writing tests directly
• Assuming it reduces assertions

2. Which of the following is a correct way to define a constant for a base URL in Selenium Java?

easy

A. final BASE_URL = https://example.com;

B. static String BASE_URL = 'https://example.com';

C. public static final String BASE_URL = "https://example.com";

D. const BASE_URL = "https://example.com";

Solution

1. Step 1: Recall Java constant syntax

   In Java, constants use 'public static final' with type and value in double quotes.

2. Step 2: Check each option

   public static final String BASE_URL = "https://example.com"; uses correct syntax; others have syntax errors or wrong keywords.

3. Final Answer:

   public static final String BASE_URL = "https://example.com"; -> Option C

4. Quick Check:

   Java constants = public static final + type + value [OK]

Hint: Remember Java constants need public static final [OK]

Common Mistakes:

• Using single quotes for strings in Java
• Omitting type declaration
• Using 'const' which is not Java keyword

3. Given the following code snippet, what will be printed?

public class Config {
    public static final String ENV = "staging";
    public static final String URL = ENV.equals("production") ? "https://prod.example.com" : "https://staging.example.com";

    public static void main(String[] args) {
        System.out.println(URL);
    }
}

medium

A. https://prod.example.com

B. null

C. Compilation error

D. https://staging.example.com

Solution

1. Step 1: Evaluate ENV value

   ENV is "staging", so ENV.equals("production") is false.

2. Step 2: Apply ternary operator

   Since condition is false, URL is assigned "https://staging.example.com".

3. Final Answer:

   https://staging.example.com -> Option D

4. Quick Check:

   Condition false -> staging URL printed [OK]

Hint: Check condition in ternary operator carefully [OK]

Common Mistakes:

• Assuming ENV equals production
• Confusing ternary true/false branches
• Expecting compilation error due to static final

4. Identify the error in this configuration code snippet:

public class Config {
    public static final String BASE_URL = https://example.com;
}

medium

A. BASE_URL should not be static

B. Missing double quotes around the URL string

C. final keyword is not allowed here

D. Class name should be lowercase

Solution

1. Step 1: Check string assignment syntax

   In Java, string literals must be enclosed in double quotes.

2. Step 2: Identify missing quotes

   The URL is not in quotes, causing a syntax error.

3. Final Answer:

   Missing double quotes around the URL string -> Option B

4. Quick Check:

   String literals need quotes in Java [OK]

Hint: Strings always need double quotes in Java [OK]

Common Mistakes:

• Forgetting quotes around string values
• Thinking static or final keywords cause error here
• Ignoring Java naming conventions (not error)

5. You want to run the same Selenium tests on different environments (dev, test, prod) without changing code. Which configuration management approach is best?

hard

A. Use external properties files to load environment-specific settings

B. Hardcode URLs in test methods and change before each run

C. Write separate test classes for each environment

D. Use random URLs in tests to cover all environments

Solution

1. Step 1: Understand maintainability needs

   Hardcoding or separate classes cause duplication and errors.

2. Step 2: Use external properties files

   Loading settings from files allows switching environments without code changes.

3. Final Answer:

   Use external properties files to load environment-specific settings -> Option A

4. Quick Check:

   External config files = flexible environment switching [OK]

Hint: Use external files for easy environment changes [OK]

Common Mistakes:

• Hardcoding URLs inside test code
• Creating duplicate test classes per environment
• Using random URLs which cause flaky tests