Skip to main content

​
Test management that belongs in the repository

OneTest TMS is a GitHub-native system for managing test cases, test runs, automated results, coverage, and reports without introducing a separate backend. Test assets remain as files. Runs and coordination use GitHub Issues and Projects. Automation uses GitHub Actions, while an MCP server gives coding agents a structured way to operate the same workflow.
Test files connected to a GitHub test run and verified coverage report

Test assets flow from repository files into GitHub-native runs and verified coverage.

View the repository

Read the documentation, inspect the implementation, and follow development.

Open the current TMS

Access the existing OneTest test-management application.

​
How it works

Tests as files

Test cases live in tests/, with project configuration in .onetest/. They can be reviewed, versioned, and changed with the product code.

GitHub as the workflow

Issues and Projects provide coordination, while committed reports preserve results and history.

MCP and CLI operation

The onetest-tms MCP server turns agent and CLI actions into GitHub operations and committed artifacts.

Automation-ready

Ingest automated results, correlate them with test assets, and report coverage through standard developer workflows.

​
Requirements

The GitHub-native TMS uses tools already common in development environments:
  • Node.js 20 or newer
  • GitHub CLI (gh), authenticated
  • Git
  • Bash
  • Python 3

​
Try it

The project works today through its MCP server and CLI. See the repository documentation for provisioning, authoring cases, creating runs, recording results, and reporting coverage.