// Desktop

QA Forge

Test your Windows software properly, and run the same tests again next month.

WindowsPythonDesktop AppQA

Not sure it fits your job? Tell us about it. We will give you an honest answer before you buy.

// the problem

Most QA on desktop software still lives in a spreadsheet. Test cases in one file, evidence in a folder of screenshots, results in an email thread — and when a release goes wrong, nobody can reconstruct what was actually tested.

// what this does

QA Forge keeps the test cases, the run, the evidence and the result in one place on the tester's machine. A cycle you ran last month can be re-run identically this month, and the report comes out of the same place the testing happened.

// features

What you get

Test cases with structure

Steps, expected results and preconditions kept as data — not as rows in a spreadsheet that everyone formats differently.

Repeatable run cycles

Start a cycle, work through it, and get the same sequence again next release without rebuilding it.

Evidence attached to the step

Screenshots and notes attach to the exact step that failed, so a bug report doesn't need reconstructing later.

Clear pass/fail reporting

Results come out as a report you can hand to a client or a release manager without reformatting it first.

Runs locally on Windows

A desktop application, not a hosted service — useful when the software under test isn't on the internet.

Exportable data

Your test cases and results are exportable, so you're never holding your QA history hostage inside one tool.

// how it works

Three steps, start to finish

01

Install on Windows

Install the desktop application on the machine where the testing actually happens.

02

Build your test cases

Add cases with steps and expected results, or import the ones you already have.

03

Run and report

Work through a cycle, capture evidence as you go, and generate the report at the end.

// licensing

Pick the licence that matches how you'll use it

You get the same tool in every plan. What changes is how many places you can use it, and how fast we answer you.

Single

One site or one machine

  • Full product, no feature limits
  • One site / one machine activation
  • Updates for the licence period
  • Included support — 48 hour response
Get a Quote

Agency

Deploy across client work

  • Full product, no feature limits
  • Use across client projects
  • Updates for the licence period
  • Managed support — 4 hour response
  • Install & setup on request
Get a Quote

Tell us which plan fits you. We send the price the same day. You are not committing to anything by asking.

// specifications

Technical details

Platform
Windows
Built with
Python
Type
Desktop application
Data location
Local machine
Minimum Windows version
Current version

Where you see a dash, we have not put a number because we will not guess one. Ask us and we will give you the exact answer for your setup.

// support

What happens after you buy

  • Help to get it installed and running. We would rather it works than leave you stuck
  • Bug fixes for as long as your licence runs
  • New versions as we release them
  • A reply inside your plan's time: 48 hours, 12 hours or 4 hours
See support plans
// faq

Questions about QA Forge

It's a desktop application that runs locally, which is deliberate — a lot of software under test sits on internal networks.
Tell us how your team works and we'll tell you honestly what the current build supports before you buy, rather than after.
Import is supported. Send us a sample of your current format and we'll confirm it maps cleanly.
No. Test cases and results are exportable — the point is to keep your QA history usable, including after you stop using the tool.
It's built around desktop software workflows. If your testing is mostly web, say so and we'll tell you whether it's a good fit.
// next step

Not sure if it fits your setup?

Tell us what you use now. If QA Forge is not the right fit, we will say so.