/// Software test automation tools
Software test automation tools: the four kinds, and what each costs to run
Every test automation tool is one of four things: a codeless recorder, a code framework, an API tool, or an execution cloud. The right question is not which is best, but who writes the tests, what format they live in, and what you pay each time they run. This page lays the four out, then shows where L3git sits.
The four kinds
| Kind | Examples | Who writes tests | You own the code | Cost to run | Works offline |
|---|---|---|---|---|---|
| Codeless recorder / low-code IDE | Katalon, Ranorex, Tosca, testRigor | Analysts, manual testers | No — proprietary format | Runtime licence per CI node or SaaS tier | Some |
| Code framework | Selenium, Playwright, Cypress, REST Assured, Appium | Engineers | Yes | $0 (your CI) | Yes |
| API tool | Postman, ReadyAPI | Either | Mostly no | Per-user cloud or per-seat + runtime | Partly |
| Execution cloud / grid | BrowserStack, Sauce Labs, LambdaTest, Kobiton | n/a (runs your tests) | n/a | Per parallel or per minute | No |
| L3git | UI, API, Suite | Analysts and engineers | Yes — standard Selenium / REST Assured / Cucumber | $0, your own agents (no Grid) | Yes, air-gapped |
How to choose
If analysts will write the tests
You need a recorder. The trap is the storage format: if the tests live only inside the vendor's tool, every renewal is a hostage negotiation. Ask to see the generated code before you buy.
If engineers will write the tests
A code framework is free and portable. The cost is authoring time; most teams find the backlog of untested flows grows faster than the engineers can script them.
If you run tests many times a day
Add up the execution tax first. Runtime nodes, parallels and minutes are the line items that double the bill in year two. Tools that generate code you run yourself have none.
If you work in government or a regulated network
Rule out anything that needs the internet to author or run. You want installed-only tooling, offline licensing, local AI, and a Section 508 audit built in.
Solutions by job
Compared with named tools
Common questions
What is a software test automation tool?
Software that runs checks against an application for you: clicking through a website, calling an API, or driving a mobile app, then reporting pass or fail. Tools differ mainly in who writes the test (a recorder or a developer), what format the test is stored in, and what you pay each time it runs.
Codeless or code-based: which should a team pick?
Codeless tools let analysts author quickly but usually store tests in a proprietary format you cannot leave with. Code frameworks (Selenium, Playwright, REST Assured) are portable but need engineers. L3git is the middle path: codeless authoring that outputs a standard code framework.
What is an execution tax?
A charge every time a test runs: a runtime licence per CI node, metered minutes, or per-parallel pricing on a cloud grid. Tools that generate plain code you run yourself have none.
Which tools work offline or air-gapped?
Open-source frameworks do, and so does L3git with an offline key. Cloud platforms, SaaS recorders and device clouds do not.
How much do test automation tools cost in 2026?
Per-seat IDEs run roughly $84 to $229 per user per month plus runtime fees; cloud grids about $199 per parallel per month; metered mobile clouds from $83 per month for 500 minutes. L3git UI is $49 per user per month with free runs.