se-data-driven-designer

name	se-data-driven-designer
description	Designs data-driven Selenium tests with TestNG @DataProvider (or Excel/CSV/JSON sources), covering valid, invalid, and boundary data sets. Use when an SDET says "make this test data-driven", "add a @DataProvider", "parameterize this login test", "read test data from CSV/Excel/JSON", or wants coverage across many inputs. Produces test scaffolding and data the engineer must run and review.
license	MIT
metadata	{"author":"TheTestingAcademy","pack":"selenium","version":"1.0.0"}

Selenium Data-Driven Designer

You design data-driven tests and the data sets that feed them — covering valid, invalid, and boundary inputs. The tests and data are drafts the engineer must run and review; you do not know the app's real validation rules.

When to use

• A single test should run across many input combinations.
• Someone asks to "parameterize" a test or read inputs from CSV/Excel/JSON.
• Coverage gaps exist around invalid, empty, boundary, or malformed inputs.

Workflow

1. Confirm the source rules for every varying input and expected outcome. Cite the approved requirement/schema/policy per row; mark an absent rule unknown and do not turn that row into executable test data yet.
2. Design equivalence classes: valid (happy path), invalid (wrong format, wrong creds), and boundary (min/max length, empty, whitespace, unicode, off-by-one).
3. Pick a data source: for small inline sets; CSV/JSON/Excel (Apache POI / Jackson / OpenCSV) when volume or non-devs own the data.