Ship & show — portfolio and interviews

as a manual tester

A great test report nobody reads helps nobody. You've always known presentation matters.

→

in automation

A great repo nobody can run is the same. The last mile — README, badge, talking points — is what converts work into a job.

Hiring managers give a portfolio repo about two minutes. This lesson makes those two minutes count.

The README that gets you interviews

README.md — the skeleton

# SauceDemo Automation Framework

![tests](https://github.com/YOU/saucedemo-automation-framework/actions/workflows/tests.yml/badge.svg)

Java 21 · Selenium 4 · JUnit 5 · REST Assured · GitHub Actions

## Run it
    git clone https://github.com/YOU/saucedemo-automation-framework
    cd saucedemo-automation-framework
    mvn test -Dheadless=true

## What's demonstrated
- Page Object Model — zero locators in tests
- Data-driven testing (CsvSource): 4 invalid-login scenarios, 3 sort orders
- Explicit-wait strategy; screenshot-on-failure evidence
- Config-driven: -DbaseUrl / -Dheadless overrides
- Parallel classes: suite runs in 38s (was 1:57 serial)
- CI: smoke on push, full nightly, artifacts on failure

## Structure
    (paste your tree here)

That badge line renders live green/red from your latest Actions run — proof the suite works today, not just the day you wrote it. Numbers ("38s, was 1:57") do more than adjectives ever will.

Résumé bullets — from this one project

Built a Java/Selenium test framework (Page Object Model, JUnit 5) covering UI and REST API layers
Implemented data-driven and parallel execution, cutting suite runtime by ~65%
Set up CI with GitHub Actions: smoke tests on every push, nightly regression, automatic failure evidence

The interview questions this project answers

Prepare a 60-second answer for each — every one maps to something you built and can open on screen:

"How do you decide what to automate?" → Suite 00's ROI filter, plus your capstone's scope discipline.
"How do you handle flaky tests?" → explicit waits, independence, the headless window-size story from NOTES.md.
"Explain the Page Object Model." → open LoginPage; show the one-file fix story.
"CSS or XPath?" → your Suite 03 answer, with the text-matching exception.
"Walk me through your framework." → the README structure section, top to bottom.

You're not a beginner anymore. You have a framework with CI, evidence handling, parallelism, and API coverage — genuinely more than some working automation engineers set up themselves. The title on your next application is QA Automation Engineer. Aim there.

⚡ exercise · ship it

Write the README with the badge and your real timing numbers; commit.
Verify the three-command run on another machine (or after renaming your local folder — closest thing to a stranger's laptop).
Draft the three résumé bullets in your own words and your five 60-second answers.
Add the repo link to your résumé and LinkedIn. Done is shipped; shipped is hireable.

references

key takeaways

A live CI badge + three-command run instructions = instant credibility.
Concrete numbers beat adjectives on résumés and READMEs.
Every classic interview question now has a demo you can open on screen.