Testiny Test Management Tool Review 2026: Features and Walk-Through
Testiny Test Management Tool Review: This updated review offers a concise exploration of Testiny’s features and functionality, together with a walk-through of its main test-management workflows.
From its intuitive user interface and real-time collaboration to BDD/Gherkin support, automated test-result management, AI assistance and integrations, Testiny aims to streamline testing across the software development life cycle.
Testiny supports both manual testing and the centralized management of automated test results. Automated tests continue to run in tools such as Playwright, Cypress, Selenium, JUnit or other testing frameworks, while their results, attachments and execution information are collected and analyzed in Testiny.
This review serves as a quick guide for QA professionals, developers, test managers and cross-functional teams looking for a modern test-management solution that integrates into existing development workflows.
Features
#1. Test Management
- Test Case Management
- WYSIWYG rich-text editor
- BDD/Gherkin test scenarios
- Attachments and images
- Attachments on individual test steps
- History of changes
- Test case templates
- Custom fields
- Test case ownership
- Requirements and defect links
- Bulk linking of requirements and defects
- Test execution
- Results for individual test steps
- Custom result states
- Comments and attachments
- Assigned testers
- Defect creation and linking
- Test Plans
- Dynamic test-case queries
- Folder-based and manual selection
- Automatically updated test-case selections
- Test Runs
- Create re-runs from selected or filtered results
- History of changes
- Immutable closed test runs
- PDF reports
- CSV and Excel export
- Milestones
- Group manual and automated test runs
- Start dates and due dates
- Progress overview
- Related requirements and defects
- Milestone reports
- Import and export
- Migration from other test-management tools
Testiny now also supports custom result states in addition to the standard Passed, Failed, Blocked, Skipped and Not Run states. For example, teams can add states such as “In Progress,” “Needs Review” or “Deferred” and optionally make them available for individual test steps.
#2. BDD and Gherkin Support
Testiny is now introducing dedicated BDD/Gherkin support.
BDD scenarios describe expected application behavior in a human-readable format using steps such as Given, When and Then. This makes scenarios easier to understand for testers, developers, product owners and other stakeholders.
#3. Test Automation
- Import automated test results using the Testiny CLI
- Submit results through the REST API
- Integrate with CI/CD pipelines
- Dedicated automation sources, runs and test cases
- Automatic creation and matching of automation test cases
- Test-result history
- Execution duration and environment information
- Screenshots, videos, logs and other attachments
- Custom result metadata
- Parallel and sharded test-run support
- Defect links and comments
- Automated-run retention and pinning
- PDF reports for automated test runs
- Link automated test runs to milestones
Testiny works with automated results from Playwright, Cypress, Selenium, JUnit, TestNG, NUnit, pytest, Vitest, VSTest, Robot Framework, Ranorex, CodeceptJS, Jest, Mocha, PHPUnit, xUnit and other frameworks that generate supported report formats.
The CLI can automatically recognize common CI environments and attach information such as the pipeline ID, build ID, commit, branch and job URL. Results from parallel jobs or test shards can also be combined into one automation run.
One important distinction is that Testiny manages and analyzes automation results; it does not replace the automation framework or maintain the automation source code. Automated test cases currently remain separate from manual test cases and cannot yet be automatically linked to them.
#4. AI Support Through MCP
Testiny provides an MCP Server that allows compatible AI assistants to work directly with Testiny project data.
It can be connected to tools such as Claude, ChatGPT, GitHub Copilot, Cursor and other MCP-compatible clients. Depending on the configured permissions, an AI assistant can:
- Search and analyze test cases
- Generate test cases from requirements or user stories
- Create and edit test cases
- Create, edit and organize folders
- Create test runs
- Add test cases to runs
- Guide test execution
- Update test results
- Add comments
- Analyze testing progress
This is an interesting approach because teams can use their preferred AI assistant instead of being restricted to an AI interface built into the test-management tool.
#5. Integrations
Testiny integrates with Jira Cloud, Jira Server and Jira Data Center, GitHub, GitLab, Azure DevOps, Linear, Redmine, Asana, Basecamp, Bugzilla, ClickUp, Confluence, Monday.com, Notion, Trello, YouTrack, Zendesk and many other issue-tracking and collaboration tools.
Requirements can be linked to test cases, while defects can be created or linked from manual and automated test runs and results.
For commonly used integrations such as Jira, GitHub, GitLab, Azure DevOps, Linear and Redmine, Testiny can search, create and link work items directly from its interface. A configurable link-based integration is also available for unsupported tools.
For CI/CD workflows, Testiny includes examples and integrations for GitHub Actions, GitLab CI/CD, Jenkins, Azure Pipelines, Bamboo, CircleCI and custom pipelines.
#6. Migration
Testiny’s migration capabilities have expanded considerably.
The in-app importer and migration guides now cover:
- TestRail
- Xray for Jira Cloud
- Xray for Jira Server and Data Center
- Zephyr
- Qase
- TestLink
- CSV and Excel
- Other tools through the CLI or REST API
The API-based TestRail and Xray importers can migrate more than only test titles and steps. Depending on the source, they can retain text formatting, custom fields, images, attachments and links to Jira requirements or other work items.
This makes Testiny particularly interesting for teams that want to replace an existing test-management tool without manually rebuilding their complete test repository.
#7. Audit, Compliance and Security
- Audit log with export
- Immutable closed test runs
- Immutable automated results
- Organization and project permissions
- Project-specific user roles
- Custom roles with granular permissions
- Permission groups
- Single Sign-On using OIDC providers
- Multi-factor authentication
- Enforced MFA
- Configurable password policies
- IP-based access restrictions
- API keys with configurable permissions
Testiny is available as the hosted Testiny Cloud service and as Testiny Server for self-hosted deployments.
Testiny Server is based on Docker and can be operated in a company’s own infrastructure. Cluster deployment options such as Kubernetes and OpenShift are also available for applicable installations.
Testiny Walk-Through
We started with a fresh account. Signing up is fairly easy, and no credit card is required. New accounts begin with a 21-day free trial.
After the trial, an account can continue on the Free plan for up to three users, subject to the Free plan’s usage and storage limits.
Throughout the application, Testiny guides you through the first steps, which makes it intuitive to get started. On the initial screen, you can either create a new empty project or add a demo project to explore the main features quickly.
After creating a demo project, you arrive at the project dashboard.
Here, Testiny provides several first steps to help us get started.
The demo project is already populated with test plans, test cases and test runs. We can invite team members, configure an integration for defects or requirements, or define custom fields for test cases.
The dashboard also gives us an overview of current testing activities and recent test results.
Custom Fields and Result States
Now let’s explore some of the settings.
I navigated to Settings and Custom Fields.
Testiny already contains configurable fields such as Priority, where we can add our own values or rename existing ones.
We can also create custom fields. For example, we could add a multi-select field to record the target environment or application area for a test case. Other available field types include numbers, URLs, dates, times, text and selection fields.
Testiny now also provides a separate configuration for custom result states.
This lets an organization extend the built-in result options to match its own testing workflow. A custom result state can also be configured for use on individual test steps.
Integrations and Administration
Let’s also explore the integrations.
I navigated to Settings and Integrations, where Testiny offers a large list of tools for requirements and defect management, including Jira, Azure DevOps, GitHub, GitLab, Linear, Asana, Redmine and Trello.
For example, an integration can be configured to manage both requirements and defects across selected Testiny projects.
The setup process differs depending on the external tool. With the more deeply integrated systems, Testiny can search for existing issues and create new requirements or defects without requiring the user to leave Testiny.
The settings area also allows administrators to:
- Create and manage API keys
- Invite and deactivate users
- Configure project access
- Create custom roles
- Organize users into permission groups
- Manage billing
- Review the audit log
- Configure Single Sign-On
- Enforce MFA and password policies
- Restrict access by IP address
The administration options have become considerably more granular and are now suitable for both small teams and organizations that need project-specific access controls.
Test Cases
Then, we finally navigate to our test cases:
Testiny organizes test cases in folders, and all tests can be viewed in a hierarchical structure.
I think it is very convenient that test cases and folders can be moved using drag and drop.
When you click a test case, its details appear in the side panel on the right.
You can see its custom fields, requirements, defects, history, comments, attachments and test steps.
Writing structured test cases is straightforward. Individual steps and their expected results are easy to create, while the rich-text editor supports tables, links, images, nested lists, code blocks and text formatting.
The editor also includes a quick-copy option for code and quoted text. You only need to click the formatted content to copy it to the clipboard, which is very helpful for commands, test data, email addresses and other values.
In the History tab, you can see changes made by you or other team members.
Files and images can be attached to the test case or to individual test steps. Test cases can also be linked to requirements in an integrated issue-tracking tool.
All defects previously linked to the test case during test runs are available from the test-case view.
BDD Test Cases
With the new BDD/Gherkin support, teams can also document expected behavior as readable scenarios using Given, When and Then steps.
This is especially helpful when QA engineers, developers, product owners and business stakeholders need to review the same acceptance criteria.
BDD scenarios remain part of the Testiny repository and can therefore benefit from the surrounding test-management features such as folders, ownership, history, requirements, test plans, runs and reports.
Test Plans
Let’s continue by checking the test plans.
I navigated to Test Plans and created a new plan. A plan can include manually selected test cases, complete folders or test cases selected through dynamic conditions.
For example, I added one condition to include all test cases with the priority “Critical” or “High” and another condition to include tests with the type “Security” or “Sanity.”
This is a very useful feature because a newly created security test case automatically becomes part of the plan when it matches the conditions.
Every new test run created from that plan therefore uses the current selection of matching test cases.
Test Runs and Re-Runs
I then clicked Create new run. Testiny immediately created a test run containing the test cases selected by the plan.
The tests can be assigned to team members, executed and given a result. Depending on the organization’s configuration, this can be one of the standard result states or a custom result state.
Results can also be recorded for individual test steps. Testers can attach screenshots, write comments and create or link defects in the configured issue-tracking tool.
Testiny now also provides a convenient re-run function. Instead of recreating a run manually, you can filter and select test cases from an existing run and use them to create a new run.
This is useful when you only need to retest failed, blocked or otherwise selected tests.
The run menu provides actions to:
- Close the test run and make its contents immutable
- Generate a PDF report
- Export the run as CSV or Excel
- Create a re-run
Milestones
Milestones provide an additional level above individual test runs.
A milestone can represent a release, sprint, version or another testing objective. It can group both manual and automated test runs, include start and due dates, and provide a combined overview of results.
Where an issue-tracker integration is configured, a milestone also shows related requirements and defects across its test runs.
Milestones can be closed to preserve their final state, and PDF reports can be created for sharing or archiving.
This is helpful for answering an important question that individual runs cannot always answer on their own: Are all testing activities for this release complete
Automated Test Results
The earlier version of this review did not explore automation in detail. This area has since become a much more substantial part of Testiny.
Automated tests run in the team’s existing framework or CI/CD pipeline. The generated report files are then submitted using the Testiny CLI or REST API.
The CLI processes the reports, creates automation runs, adds their results and uploads linked screenshots, videos, logs or other artifacts.
Testiny groups runs by a configured source, such as:
- Frontend unit tests
- Backend unit tests
- End-to-end tests
- API tests
- Integration tests
Within Testiny, we can inspect the result, error details, duration, execution history, CI environment, build information and attachments.
Automated runs can also be linked to defects and milestones, commented on, included in PDF reports and closed to preserve their final state.
Testiny additionally supports more advanced CI workflows such as parallel jobs and test sharding. Results from several jobs can be grouped into the same automation run without manually passing a Testiny run ID between jobs.
AI Support With the MCP Server
Another major addition is the Testiny MCP Server.
After connecting Testiny to an MCP-compatible AI assistant, the assistant can access Testiny through a set of permission-controlled tools.
For example, you can ask the assistant to:
- Find existing tests for a feature
- Analyze a group of test cases
- Generate test cases from a requirement
- Create or edit test cases
- Organize tests into folders
- Create a test run
- Add selected tests to the run
- Record test results
- Summarize testing progress
This allows Testiny data to become part of AI-assisted development and QA workflows without requiring teams to use only one specific AI product.
Importing Test Cases and Migrating From Other Tools
We now create a new empty project by clicking the dropdown next to the project name in the toolbar.
In the empty project, we navigate to Test Cases and select Import.
Testiny provides several options:
- Import from CSV or Excel
- Import through the TestRail API
- Import a TestRail XML file
- Import from Xray for Jira Cloud
- Import from Xray for Jira Server or Data Center
- Import from Zephyr
- Use the Testiny CLI
- Use the REST API
Migration guides are also available for Qase and TestLink.
The API-based importers can preserve significantly more data than a simple spreadsheet import, including custom fields, rich-text formatting, images, attachments and linked work items where supported by the source system.
The CLI and REST API can also be used to import test cases or submit automated test results as part of a custom workflow.
Pricing Details
Testiny now offers four main cloud plans:
- Free: $0 for up to three users
- Starter: starting at $18.50 per user/month
- Business: starting at $20.50 per user/month
- Enterprise: starting at $30 per user/month
- Custom Enterprise/Testiny Server: individually quoted
The available functionality differs by plan. For example, Business adds automation, milestones, custom result states and Single Sign-On, while Enterprise adds capabilities such as custom roles, permission groups, project-specific roles and the audit log.
Lower-priced Viewer seats are available for users who mainly need to view and comment on testing data.
Volume discounts are available, and annual subscriptions include two months without charge. Testiny also offers a 21-day free trial without requiring a credit card.
After the trial ends, the account can continue on the Free plan for up to three users. Testiny also provides special conditions for open-source projects, educational organizations and non-profit organizations. Prices are stated excluding applicable taxes.
Verdict
Testiny impresses me with its very good usability, short learning curve and modern interface.
Its test-management functionality has grown substantially since the earlier version of this review. In addition to test cases, plans and manual runs, Testiny now provides milestones, custom result states, dedicated automation-result management, broader migration options, AI support through MCP, more granular permissions and a self-hosted edition.
The new BDD/Gherkin support is another useful addition, especially for teams that want business-readable scenarios to remain connected to their broader testing workflow.
I particularly liked:
- The fast and intuitive interface
- Dynamic test plans
- Custom fields and result states
- BDD/Gherkin support
- Manual and automated testing visibility
- Milestone-based release tracking
- Extensive issue-tracker integrations
- Migration from TestRail, Xray and Zephyr
- AI integration through MCP
- Cloud and self-hosted deployment options
Features I would still like to see include reusable manual test steps and direct linking between corresponding manual and automated test cases. At present, automated test cases remain separate from manual test cases.
In summary, Testiny is a recommended choice for teams seeking a modern and flexible test-management platform. It combines an approachable user experience with increasingly comprehensive capabilities for manual testing, BDD, automation-result management, integrations, AI-assisted workflows and enterprise administration.
Go to Testiny and start your free trial today.
Related posts:
