Why Properties file for configuration in Selenium Java? - Purpose & Use Cases

The Big Idea

What if you could change test settings without touching a single line of code?

The Scenario

Imagine you have a test script that needs to run on different websites, browsers, and user accounts. Every time you want to change the browser or URL, you open the code and change values directly inside it.

This means you must edit and recompile your test code for every small change.

The Problem

Changing values inside the code is slow and risky. You might accidentally break the code or forget to change all places. It's hard to keep track of settings, and sharing tests with others becomes confusing.

Manual updates cause errors and waste time.

The Solution

Using a properties file lets you keep all settings like URLs, usernames, and browser types outside the code. Your test script reads these values at runtime.

This means you can change configurations anytime without touching the code, making tests flexible and easy to maintain.

Before vs After

✗ Before

String url = "http://testsite.com";
String browser = "chrome";

✓ After

Properties prop = new Properties();
prop.load(new FileInputStream("config.properties"));
String url = prop.getProperty("url");
String browser = prop.getProperty("browser");

What It Enables

It enables quick, safe changes to test settings without rewriting code, making automation scalable and less error-prone.

Real Life Example

When running tests on a new website version, you just update the URL in the properties file. Your test script automatically uses the new URL without any code changes.

Key Takeaways

Manual code changes for settings are slow and risky.

Properties files separate configuration from code.

This makes tests easier to update, share, and maintain.