Framework Milestone 7: Data and Journeys

Why it matters

Real suites cover many inputs and several users. Data-driven tests and tagged suites let you add cases without new code and choose what runs when.

What to build

Data-driven validation. One registration test fed from a CSV or JSON file of invalid inputs (an underage date of birth, a bad postal code for the country, a weak password), each with the message expected.
A permissions matrix. One test that runs for each role and page, checking who can open what: a customer on /cover/queue sees "You don't have access".
The full claim journey. A customer files a claim above the adjuster's limit, the adjuster recommends it, the manager approves a lower payout, and the customer sees it, each in their own browser session.
Tags. Mark tests as smoke or regression, and run either group from the command line.

Rules

Test data files hold inputs and expected results, not code.
Generated data such as descriptions and amounts is random enough not to clash between runs.
Every role in a journey has its own session; none signs out and back in mid-test.

Hints

Selenium

Use your runner's data features: TestNG @DataProvider, JUnit @ParameterizedTest, pytest parametrize, NUnit TestCaseSource. Run separate drivers for each role in the journey.

Playwright

Loop over the data to create one test per case, and use browser.newContext() for each role. Tag with @smoke in the title and run with --grep.

These are pointers, not solutions. TestDojo doesn't publish a finished framework: the point is that you build and understand your own.

Done when

Adding a validation case needs only a new row in a data file
The permissions test covers every role
The full claim journey passes, with each role in its own session
Smoke and regression runs can be started separately
No test depends on data left behind by another

Ticks are saved in this browser only, for your own tracking.

In an interview

Questions this milestone prepares you for, and what a good answer covers. Answer them in your own words, about your own framework.

How do you manage test data?: External files, generated data, creating it through the API, and cleaning up or resetting.
What is data-driven testing?: One test, many inputs, with the inputs and expectations kept outside the code.
How do you choose what runs in a smoke suite?: The critical paths that must work for a release, kept fast; the rest in regression.

Note the decision you made in this milestone and why. Those notes become your README in milestone 9.

Test data and full journeys