Separation of data from scripts

The Core Principle

Keeping test data (inputs, expected outputs) separate from the test automation logic makes tests easier to maintain, extend, and understand.

How It's Done

• Storing test data externally in Excel, CSV, JSON, or a database rather than hardcoding values in scripts.
• Using data providers (like TestNG's @DataProvider) to feed external data into a single reusable test method.

Why This Matters

When data is separated from scripts, adding new test scenarios becomes a data-entry task rather than a coding task, and non-technical team members can contribute test cases directly.