In plain English.

You don't have the budget, tools, headcount, or stable system under test that automation needs. The product ships anyway. How do you run real testing on a shoestring?

This talk answers:

• How to size the manual effort honestly — with two rules of thumb your CFO will believe.
• Where to find good testers cheaply — and what each hiring pool's weakness is.
• How to train, shift, and supervise a lean manual team.
• Which tests you cannot run manually, no matter how tight the budget.

Written for founders, engineering leads, and QA managers at small or early-stage companies.

The field test.

Five obstacles.

• SUT changes frequently — scripts break faster than you write them.
• No budget or calendar for script development.
• No suitable tool at a justifiable price.
• Team lacks automation skill or experience.
• Critical risks aren't amenable. Usability, localization, error handling, installation, docs — cheaper and more honest manually.

Six productive test hours

per 8–10 hour day.

Testers do not test for eight hours.
Testers test for six, and spend the other two fighting their environment.

Bug reporting, status documentation, communication, breaks, blocking issues, debugging — it's part of the job, not an excuse.

25% downtime on good builds.

75% downtime on bad ones.

Four days of calendar to get one day of test coverage, on a bad build.

Budget the worst case up front. Do not promise a schedule without it.

Three roles. Leveraged.

Four cheap sources.

Pick the mix that fits your product and your office culture.

Universal skills vs. company rituals.

The technician who cannot reproduce and document a bug is broken in a way a second badge tour does not fix.

Ten-step bug report.

Every technician has to be fluent in one thing above all others.

Investigation half: structure · reproduce · isolate · generalize · compare.
Writing half: summarize · condense · disambiguate · neutralize · review.

Grammar and spelling count. A poorly written report can render a technically correct one ridiculous.

See /resources/qa-library/bug-reporting-process for the full checklist.

Same salary envelope.

More coverage.

Night (~4 PM–1 AM) and graveyard (~midnight–9 AM) shifts stretch a shoestring team.

The line you do not cross.

Even a shoestring program buys or builds some automation for the right column.

It's a solution, not a concession.

Bring a plan, not a request for more money.

• Flexibility and responsiveness — technicians ramp fast.
• Cost and coverage — cheaper bodies = more coverage on the same budget.
• Schedule — test cycle time goes down.
• Staff retention — test engineers burn out less when they have technicians to delegate to.
• Career development — helps inexperienced people jump-start technical careers.

Four to hold against.

• Total automation is a goal, not a precondition. Manual program bridges "nothing" and "right automation, right time."
• Budget the overhead before the test count. 6 hours, 75% downtime. Plan them in.
• Leverage from the org shape. Manager + engineers + many technicians. Flat senior teams run out of money before tests.
• Pick manual for what humans judge best. Usability stays manual. Load stays automated. Even on a shoestring.

Using manual testing inappropriately can mislead people about the extent of test coverage. Using automation inappropriately usually just fails.