Skip to content
Testiny logo

Testiny

Stores manual and automated test cases, imports Playwright, Cypress and JUnit results into one report, and syncs issues with Jira or GitHub.

Free plan · From $18.50/user/moActively maintained

AutomationEnterprise
testiny.io ↗LinkedInInstagramFacebookYouTubeX
Open testiny.ioAlternativesSet it up for my teamIs Testiny yours? Claim the card →
At a glanceswept Oct 14, 2026

≈ 597visits/mo

Established · estimate, read Oct 14, 2026

For
QA teams that want manual test cases and automated results managed in one system
Price
Free plan · From $18.50/user/mopricing page, read Oct 15, 2026Trial & discounts: 21-day free trial
Activity
Actively maintainedrelease 9 days ago
Company
Mategra GmbH · since 2021 · ~6 peopleprivacy policy · per their site · per their About page
Runs as
Self-hosted
Used for
  • import test cases from TestRail, Zephyr, or Xray
  • link test failures to Jira, GitHub, or GitLab issues
  • consolidate Playwright, Cypress, and JUnit results into one report
read off testiny.io on Oct 15, 2026
Worth knowingcomputed from what we read · each with its source
  • Used more than 79% of the 168 tools on its shelfINITE Atlas →
  • On the web since 2021, older than 74% of its shelfINITE Atlas
  • 56,143 installs a month on npmpublic registry
  • Has an MCP server (1 in the registry)public registry →
Pricingpricing page, read Oct 15, 2026

Free plan · From $18.50/user/mo

Trial & discounts 21-day free trial

pricing page

The companyeach fact with its source · read Oct 17, 2026
Your datawhat they publish, each line with its page · read Oct 15, 2026

These are Testiny's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

How a program reaches itfound, not claimed · read Oct 15, 2026
  • MCP serverio.testiny/testiny-mcpverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-15
  • Address to connectapp.testiny.io/api/v1/mcp-server
  • API docstestiny.io/apithe vendor's page ↗
  • MCP docstestiny.io/ai-support-mcp-serverthe vendor's page ↗
  • Status pagelinked from the homepagestatus.testiny.io ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Automationby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Testiny with

Pick up to two.

All 10 alternatives to Testiny →

All Automation tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Testiny for?

Sign in to leave a note
Questions this page answers
  • What is Testiny?

    Stores manual and automated test cases, imports Playwright, Cypress and JUnit results into one report, and syncs issues with Jira or GitHub. It is listed in the Atlas under Automation and made by Mategra GmbH.

  • Who is Testiny for?

    QA teams that want manual test cases and automated results managed in one system

  • How much does Testiny cost?

    Testiny has a free plan; paid plans start at $18.50/user/mo, per its pricing page on 2026-10-15.

  • Is Testiny free?

    Yes, Testiny has a free plan, per its pricing page on 2026-10-15.

  • Do people use Testiny?

    Established: ≈ 597 visits/mo · estimate, 2026-10 · 56.1k installs/mo (npm).

  • Is Testiny still maintained?

    Actively maintained: release 9 days ago.

  • Who owns Testiny?

    Testiny is run by Mategra GmbH, per its privacy policy (2026-10-15).

  • Does Testiny have a free trial?

    Yes, a 21-day free trial, per its pricing page (2026-10-15).

  • Does Testiny give refunds?

    In its own words (terms of service, 2026-10-15): “All fees paid by the Customer are non-refundable.”

  • What are alternatives to Testiny?

    In Automation, by use: Qase.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk