By Testfort · QA framework

From requirements to production-grade tests in minutes.

TestForTge is an AI-assisted QA framework that turns specs, docs and live URLs into structured test cases, checklists, Playwright scripts and exec-ready reports — without abandoning your team's process.

Request a demo → See how it works

What TestForTge does for your QA team

Six core capabilities. One Flask app. No vendor lock-in — every artefact exports to the tools you already use.

Requirement ingestion

PDF, DOCX, XLSX, CSV, MD, plain text — or a live URL. Crawls, parses, extracts atomic user stories with categories & priorities.

Test cases & checklists

Positive, negative and edge-case test cases reviewed by a built-in QA Lead pass. Compact checklists in the TestFort format. Exports to MD / HTML / CSV / XLSX.

QA estimation

PERT-based hours from the same input — minutes-per-TC × features × platforms, with compatibility, bug rate and PM overhead applied. Full XLSX breakdown ready for clients.

Manual & automated execution

Step-by-step manual runs with environment + credentials capture, or one-click Playwright headless automation with video and screenshot artefacts.

Bug reports & metrics

Structured bug forms (severity, priority, repro steps, attachments). One-click Markdown export of the whole bug base. Live status & coverage dashboards.

Tedgie — QA assistant

Built-in AI chat with context of your project. Answers questions about Estimation, Test Cases, Automation, and generates bug-form drafts on demand.

How we work together

From the first dropped spec to a deployable QA pack — clear roles, shared workspace, real-time iteration.

testfortge.app/test-cases
↑
Drop spec, screenshots, video — or paste a URL
▸ https://shop.example.com/checkout
▸ requirements_v3.pdf 2.4 MB
▸ wireframes.docx 786 KB
SourceMulti-input · 64 MB cap
You

01.You drop the requirements

Paste a feature URL, upload a PDF/DOCX/XLSX, or just type the user stories. TestForTge accepts whatever format the dev team gave you.

  • 9 supported file types + crawl-on-URL
  • 64 MB upload cap per request
  • Saved to a versioned project snapshot
parser · user-stories
parsed 9 categories 47 stories
P1 As a guest, I want to add an item to cart without signup
P1 As a user, I want to apply a promo code at checkout
P2 As an admin, I want to override pricing on a single SKU
P3 As a returning user, I want my address auto-filled
+ 43 more · click any story to drill into traceability
TestForTge

02.We parse, classify, prioritise

The framework breaks the input into atomic user stories, assigns priority and category, and builds a story ↔ test-case traceability matrix automatically.

  • Persona & role detection (guest / user / admin)
  • Page-number / artefact scrubbing on PDFs
  • Saved to your project — re-runnable any time
generated · 218 test cases
Test Cases Checklist Estimation
PASSTC-018Verify that adding 2 items updates cart total
PASSTC-019Verify that promo PROMO10 reduces total by 10%
REVIEWTC-020Verify negative quantity is rejected client-side
EDGETC-021Verify cart with 999 items doesn't time out
Coveragepositive · negative · edge
TestForTge

03.We generate the QA pack

Test cases (positive / negative / edge), TestFort-format checklists and PERT-based hour estimates. Reviewed in the same pass by a built-in QA Lead module that fixes voice drift, dup IDs and page-number leftovers.

  • Markdown · HTML · CSV · XLSX exports
  • Compatible with TestRail, Zephyr, qase.io
  • Estimation breakdown shipped as a separate workbook
execution · live
Manual run · QA
142 PASS 3 FAIL 2 BLOCK
Automation · Playwright
42 PASS 1 REVIEW
Pass rate96.6 %
▸ video.mp4 · screenshots · har trace per step
You + TestForTge

04.You run, we record

Step the team through manual cases — or hand the same set to Playwright headless. Either way TestForTge captures pass/fail/blocked, environment, and per-step artefacts.

  • Async job queue · 429 with Retry-After on overflow
  • Screenshots, video, HAR per Playwright run
  • Auto-generated test accounts on demand
delivery · qa-pack-v3.zip
Test cases 218 · XLSX, MD Checklist 1 · TestFort format Estimation 84.5 h · PERT Bug reports 7 · severity-coded Automation runs 3 · video + HAR
XLSX Markdown CSV HTML TestRail Zephyr qase.io
TestForTge

05.We deliver a deployable QA pack

Everything is exported as one self-contained pack — ready to share with stakeholders, drop into your tracker, or hand off to the next sprint's regression run.

  • Stakeholder-friendly XLSX/MD reports
  • One-click re-run on a new release
  • Project snapshots — restore any past state
Powered by
Flask 3.1 Playwright 1.49 Anthropic Claude openpyxl · pypdf Testfort QA process

The framework is engineered in-house at Testfort and battle-tested on real client engagements. Every line of generated content is reviewable, exportable and free of vendor lock-in.

Frequently asked questions

Short answers from real client conversations — open any item to expand.

Is TestForTge self-hosted or a SaaS?
Self-hosted. It's a Flask application you run on your own infrastructure — Docker, a VM, or bare-metal. Specs, generated artefacts and bug reports never leave your network. No data is sent to a third party unless you explicitly turn on the optional AI mode.
What inputs does it accept?
PDF, DOCX, XLSX, CSV, MD, TXT, HTML, PNG/JPG and short videos as evidence — plus a live URL crawler that extracts features straight from a deployed page. The framework normalizes everything into atomic user stories with categories, priorities and a story ↔ test-case traceability matrix.
Does it replace my QA team?
No — it removes the boilerplate hours. TestForTge produces a first draft: structured test cases (positive/negative/edge), a TestFort-format checklist, a PERT-based estimation and Playwright scripts. Your QA Lead reviews and adjusts before signing off. The built-in QA-Lead pass already fixes voice drift, duplicate IDs and PDF artefacts before you see the output.
Can I use it without sending data to an LLM provider?
Yes. The default mode runs entirely offline: rule-based generators for test cases, checklists, estimation and the Tedgie chat assistant. AI mode is opt-in via an Anthropic API key when you want richer free-form suggestions — turn it on in .env, turn it off any time, no migration required.
Will the exports work with TestRail / Zephyr / qase.io?
Drop-in. Test cases and checklists export to Markdown, HTML, CSV and XLSX in column shapes those tools accept directly. Estimation ships as a separate XLSX workbook with the full breakdown — minutes-per-TC × features × platforms, compatibility, bug rate and PM overhead — ready for client sign-off.
How does the built-in automation work?
One click. The framework synthesises Playwright scripts directly from your test cases, runs them headless in Chromium, and captures video, screenshots and a per-step HAR trace. Async job queue with a per-session concurrency cap means you can launch a new run while a previous one is still finishing.
What about security & compliance?
CSRF on every state-changing request, HttpOnly + SameSite cookies, strict CSP, path-traversal guards on asset serving, optional Basic-Auth gate for shared deployments. All session data is filesystem-bound and rotated on server restart. Threat model and security posture are documented in the framework's REQUIREMENTS.md.
How do I try it on my project?
Book a 30-minute walk-through with our QA team. Bring a real spec — a PDF, a Confluence page, a URL — and you'll leave the call with a generated draft test plan and an estimation workbook for your stack. Pricing and engagement model are scoped on the call.

Ready to ship QA faster?

Book a 30-minute walk-through with our QA team — bring your spec, leave with a draft test plan.

Request a demo → Visit testfort.com