Blog
Manual testing without a test management tool
How to do manual testing without TestRail or a heavy TMS: cases in Excel, evidence per step, and a report your team can actually open.
2026-05-15
The spreadsheet still works
Plenty of teams never buy TestRail or Zephyr. They keep cases in Excel, run them by hand, and paste results into an email at the end of the week. It works until it does not: version chaos, missing screenshots, defects that nobody retests.
Manual testing without a test management tool is not reckless. It is realistic for small teams, contractors, and side projects. The fix is not always a six-figure TMS. Sometimes you need cases in a structured file, a runner that records status per step, and an export stakeholders can open without an account.
What you actually need
- Test cases with IDs and expected results
- A way to mark Pass / Fail per step during the run
- Screenshots tied to the step that failed
- A defect log linked to the run
- A PDF or Excel summary for the release meeting
Lightweight manual testing workflow
This is the manual testing process most small teams can run every sprint without buying seats in a cloud TMS.
- Write cases: Excel or CSV with TC_ID
- Import: Load into side panel
- Run steps: Pass / Fail per step
- Capture evidence: Screenshot on failure
- Log defects: Linked to step
- Export report: PDF or Excel summary
TMS vs lightweight workflow
Enterprise TMS vs Excel + side-panel runner
| Need | Heavy TMS | Lightweight workflow |
|---|---|---|
| Manual step execution | Yes, often clunky in browser | Built for side-panel runs |
| Per-seat cost | Monthly per user | Free extension + your spreadsheet |
| Offline / local data | Usually cloud-only | Stored on your machine |
| Import from Excel | Sometimes extra setup | Native .xlsx and .csv import |
| Screenshot per step | Varies by tool | One click from runner |
| Best for | Large orgs, Jira integrations | Small teams, freelancers, MVPs |
Manual testing with Excel: one sprint walkthrough
Sprint 14 — Auth module, no TMS
Monday: Download the test case template. Write twelve cases for login and password reset. Save as sprint14-auth.xlsx.
Tuesday: Import into QA Workspace. Run against staging build 408. Four steps fail — two defects logged with screenshots.
Wednesday: Dev fixes land on build 409. Retest the same steps from Tasks. Close both defects.
Thursday: Export PDF run summary. Attach to release Slack thread. PM has pass/fail counts without a TMS login.
Where a side panel helps
QA Workspace lives in the Chrome side panel next to the app under test. Import your spreadsheet, run steps with keyboard shortcuts, capture screenshots, log defects, and export a report. Data stays on your machine.
If you are paying per seat for a TMS and only using manual execution, try running one sprint with a free import + export workflow first. You might find the heavy tool was solving problems you never had.