Milestone 9 of 9
Portfolio and interview
Someone who has never seen your repository understands what it does, how it's built and how to run it, and you can walk them through it in a few minutes.
Why it matters
An interviewer may give your repository two minutes. A clear README and a practised walkthrough turn "I built a framework" into evidence. This milestone is optional if you only want the experience.
What to build
- The README. What it is (a framework for DojoCover, a practice app), the tools and why you chose them, the folder layout, how to run it locally and in CI, and the CI badge.
- An architecture picture. A simple diagram or list of the layers: tests, page and component objects, the API client, test data, configuration and utilities, and how a test flows through them.
- Your decisions. A short section on the choices you made and why, from the notes you kept in each milestone: assertions in tests or pages, how waits work, how you handle data.
- Proof that it works. A screenshot of a report and of a green scheduled run, or links to them.
- A tidy history. Commits with clear messages, no secrets anywhere in the history, and no leftover experiments.
- A walkthrough. Practise a two-minute tour: the problem, the layers, one test end to end, and the CI run. Then practise the interview questions from every milestone.
Rules
- Make the repository public only if you want it in your portfolio, and check the whole history for secrets first.
- Say plainly that it tests DojoCover, a practice app on TestDojo.
- It must be your own work. You will be asked why you made each decision, and copied code won't hold up.
Hints
Selenium
Reviewers look for a clean page layer, explicit waits, a driver factory and parallel-safe drivers. Show where each lives.
Playwright
Reviewers look for fixtures, sensible locators, API setup and the config. Show your fixtures and one hybrid test.
These are pointers, not solutions. TestDojo doesn't publish a finished framework: the point is that you build and understand your own.
Done when
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.
- Walk me through your framework.
- The problem, the layers, one test end to end, and how it runs in CI, in about two minutes.
- What would you change if you started again?
- An honest trade-off you'd revisit, and what you learned from it.
- How would this scale to a team of five?
- Conventions, code review, shared components, test data ownership, and keeping CI fast.
Note the decision you made in this milestone and why. Those notes become your README in milestone 9.