Learn about Testiny’s application structure and its entities, the technology Testiny is built on, and its vision for the future.
When you use Testiny, you’re part of one or more organizations. Usually, a company uses one organization. You can use one email address to create or belong to several organizations.
A test case is sort of the "base" entity in Testiny. It generally describes the steps to be executed, can have different properties in the form of custom fields, and is organized in folders. To achieve traceability, test cases can be linked to requirements. Test cases have a natural sort index, so the order within a folder can be changed and is saved by Testiny.
Test runs represent a collection of test cases to be executed. A test run sums up all the results of its test cases and gives an overview of the testing status.
They are designed to represent all executed tests e.g. for a specific release (like v1.7.4) of a product. Within test runs, test cases are assigned to individual users.
Test runs can be closed and are then sealed, which prohibits any further changes to test cases and their results. Thus, if a test case is changed, a closed test run retains all properties (steps, fields, results, ...) of the moment in time when the run was closed.
Test runs or test case executions can be linked to defects for proper traceability.
A test plan is a meta-layer between test cases and test runs that stores additional "generic information" for the later creation of test runs.
Examples would be test plans for major-, minor-, or bugfix releases, but not for a specific release. A bugfix release plan would typically contain a very limited number of test cases, while a major release plan would contain (almost) all cases. Other examples would be plans for specific features, app regions, ...
A test plan is linked to all test runs created from it. It is loosely coupled and provides an additional layer of freedom.
Executing a test plan results in a test run with all the properties defined in the plan (e.g. which environments to use, etc.)
Requirements and Defects
Linking requirements and defects stored in other tools (e.g. Jira, Azure DevOps, GitHub, GitLab, Redmine ...) is also supported by Testiny. Requirements can be linked with test cases and defects can be linked with test runs or test case executions. Depending on the requirement or defect management tools, bi-directional linking is possible as well. This allows you to see the test cases associated with a requirement directly from e.g. Jira.
When entities are deleted, they are first moved to a trash bin, but still kept in the database even after the trash bin is emptied, so only a soft delete is performed. So, whenever you’re deleting something unintentionally, we’ll be able to restore it.
This is a pro feature and not available in the free plan.
Maybe you’ve noticed the immediate updates across all connected users and browsers whenever you’re making a change in Testiny. The whole application relies on a sophisticated message-bus model in the background, where all browser sessions of your organization receive updates in real-time.
Give it a try — open two tabs and make some changes in one tab, and the changes appear immediately in the other tab.
This also works when working together with colleagues. Everybody receives changes instantly; no more hitting "F5" to refresh.
For this feature to work properly, please ensure that your firewall provider allows websocket connections.
Testiny is built as a "single page application" (SPA), relying on a separation of backend and frontend. All communication between the front end and the back end is handled via REST calls, so using the Testiny API, you can rebuild everything the front end can do. The websocket connection is used to push updates and notifications immediately to other clients.
Testiny in General
The main idea behind Testiny was to build a modern web-based test management tool that does not feel like working with a website.
A strong focus was placed on performance and ease of use as Testiny should nearly feel like using a desktop app. And ideally, you should never need this documentation as everything is self-explanatory.
Whenever you have any questions, ideas, comments, but also complaints, just reach out to us. We’re always there to help you and have an open ear for all of your feedback. Either use Testiny’s built-in feedback system, check out the forum or write us an email to: [email protected]
Testiny is built in Austria in the middle of Europe, so we take security and data integrity very seriously. Testiny follows a minimum data policy, so we just collect the most essential data and everything is handled according to the strict European GDPR or even stricter.
So, with Testiny, you’ve found a safe home for your tests and your data. In case you ever manage to break into our systems, please send us your CV. ;-)
As a little teaser for those who have read this site until the end, we’re working on something very special behind the scenes. It should bring testers and developers much closer together and provide a massive boost in terms of traceability when it comes to test cases and what’s really going on inside the app. Stay tuned and feel free to reach out to us if you want to know more.