What it does
Testiny stores manual test cases, plans, runs and execution history alongside results from automated tests. Teams can organize tests in folders, write step-based or BDD cases, assign runs, and import supported report files through its CLI or API. It is a test-management and reporting layer, so the team's own framework or CI pipeline still executes the tests.
Turn test cases into a release run
Testiny's tutorial starts by grouping cases into folders and choosing a template: step-by-step checks, free-form text for exploratory work, or Gherkin for BDD scenarios. A plan can collect cases by folder, conditions or a selected list. Create a run from the plan, assign its cases and record each outcome; the runner also supports comments, attachments and execution history.
For automated suites, run tests in the team's existing framework, generate a supported report and upload it with the Testiny CLI. The import flow creates an automation run and associates the results with a project and source, so manual and pipeline results can be analyzed together. This means Testiny needs the team's report output and an API key for automated imports, rather than replacing the test runner. The official pricing documentation lists a free plan for up to three users and paid plans; it also documents a self-hosted Testiny Server option for custom enterprise terms.
Strengths
- Manual test cases support step, text and BDD templates, with plans that can collect cases statically or by conditions.
- The CLI accepts reports from several testing frameworks and adds automated results to Testiny runs.
- Manual execution history and imported automation results can be kept in the same test-management workspace.
Watch out for
- Testiny records and analyzes automated results but does not run the team's tests; the user must generate a supported report and provide an API key to import it.
Best for
- Small QA groups that want a no-cost test-management tier for up to three users.
- Teams that need reusable test plans and manual execution records.
- CI teams that want to combine reports from existing automation frameworks with manual test runs.
Sources
- Testiny Tutorial (Oct 25, 2026)
- Pricing and Payment Details (Oct 25, 2026)
- Automation Quickstart (Oct 25, 2026)
- Automation (Oct 25, 2026)