TestHero.io: the test management tool we are building
TestHero.io is our own test management tool. We are building it because we know what testers miss in tools of this kind, and what gets in their way. It is still in development and not publicly available. Here is what it already does.
Test cases
Cases are organised into projects and sections. Each has a priority, steps with an expected result, and its last status. Steps repeated across cases can be shared. Deleted items go to a trash they can be restored from.

Test runs
A run is a selection of cases to go through, for example before a release. The tester walks through the cases one by one and records the result. The overview shows how many passed, failed and remain.

Reports
The reports page shows the distribution of statuses, the pass rate over time, and a comparison of projects. The data can be exported.

CI integrations
Nobody should retype the results of automated tests by hand. TestHero.io receives them from GitHub Actions, GitLab CI and Azure DevOps and creates test runs from them.

How it is built
- Nuxt 4 and Vue 3 with Vuetify 4 on the frontend, TypeScript throughout.
- Prisma and PostgreSQL for the data.
- Two roles, manager and tester. New users are invited by a manager. There is no public sign-up.
- The interface is in Czech and English.
Security was not left for the end: passwords are stored with Argon2, login is rate-limited, forms are protected by a CSRF token, and pages send a strict Content Security Policy.
Tests
A tool for testers without tests would be a bad joke. The current state is 1,718 unit tests and 139 end-to-end tests in Playwright that run against a clean database.
What comes next
Before version 1.0 we still need to verify the Azure DevOps integration against a real organisation and finish the release steps. When the tool is out, we will write about it here.