Working repository for re-platforming OneTest (onetest.ai,
onetest-ai) to a git-native architecture with no backend
services — test assets as files, runs as Issues/Projects, behaviour as GitHub Actions + an
onetest-tms MCP server driven by the web-qa
agent family.
The TMS is operated through the onetest-tms MCP server (onetest-tms/) — a
local stdio process that turns agent tool calls into GitHub Issues, Project items, and committed
reports. Test cases live in tests/; config in .onetest/.
- Documentation — the OneTest TMS manual: Introduction · Quickstart · Guides · Reference.
onetest-tms/— the MCP server + gh-CLI engine (scripts/).skills/onetest-tms— the companion skill for agents consuming the TMS.- For contributors: the design & analysis behind it lives under
design/github-native/anddesign/functionalities/design/data-model.
The MCP server is Node, but its engine shells out to standard CLI tools, so the machine that runs
it (your laptop, or a CI runner) needs these on PATH:
| Tool | Why | Check |
|---|---|---|
| Node ≥ 20 | runs the MCP server (npx -y @onetest/tms) |
node -v |
gh (GitHub CLI), authenticated |
all GitHub reads/writes (Issues, Projects, repos) | gh auth status |
git |
clones/pulls the target repo, commits reports | git --version |
bash |
runs the engine scripts | bash --version |
python3 |
front-matter parsing, OQL, coverage, report rendering | python3 --version |
gh needs repo + read:org scopes (and admin:org / project for one-time org setup). On
macOS/Linux bash + python3 are usually present; otherwise install them (e.g. Homebrew). Run
onetest-tms doctor (or bash onetest-tms/scripts/doctor.sh) to check everything at once.
The engine is Bash + Python — there are no .bat/PowerShell scripts. On Windows, run everything
from Git Bash (bundled with Git for Windows, which you already
need for git), not cmd or PowerShell. Install a native Windows python3 (from
python.org or the Store) and make sure it's on PATH inside Git Bash.
That combination is supported; gh, git, bash, and python3 must all resolve on the Git Bash
PATH (onetest-tms doctor verifies this).
In scope: test case management, test execution management, automated test results, correlations & reporting. Out of scope: pipelines, credpools, billing/metering.
The TMS works today via the onetest-tms MCP/CLI — published to npm as
@onetest/tms (npx -y @onetest/tms): provision a
repo, author cases, create runs, record results, ingest automated results, and report coverage —
all backed by GitHub. Remaining packaging step: strip the engine out of generated product repos
so they're content-only.