Why SquashTM
Central, integrated, sovereign
SquashTM centralises all testing activity, integrates with your software delivery chain and leaves you in control of your data and where it is hosted.
A central repository to build a lasting test asset
SquashTM brings the whole testing activity into a single tool: scoping, design, execution and history. The repository is built during the BUILD phase, from requirements drawn from your user stories or specifications, then kept up to date during the RUN phase with every change to the application. Your application is thus documented in SquashTM, which becomes its living memory.
Adopted in banking, the public sector, industry and insurance, it meets the needs of contexts where validation must be formalised, traceable and auditable.
No. The Requirements and Test cases workspaces are independent: you can write and run test cases without entering a single requirement, and link requirements later. Linking becomes necessary if you want to track coverage, since the coverage rate shows whether a requirement is verified by at least one test case. It is also needed for AI-assisted test case generation, which starts from an existing requirement.
Yes, both ways. The link is created from a requirement's page, by dragging and dropping one or more test cases or through the search tool, and then appears on both sides.
A new version of the requirement is created. Versions coexist and remain independent of one another, each with its own content, life cycle and linked test cases, so the history of what was expected at each version remains available.
Yes. Permissions are granted per project, individually or by team, according to profiles whose rights are detailed in a permission matrix. A team only sees the projects it has access to.
Up to 8,000 users per instance.
A tool integrated with the whole software life cycle
SquashTM adapts to the toolchain already in place: it synchronises requirements from your GitLab, OpenProject or Jira tickets, reports issues directly in your bug tracker and retrieves execution results from your pipeline. Testers regain their place in the delivery cycle, and everyone follows test progress from the tool they already use.
Organise your tests by sprint and track user story validation from one iteration to the next. The sprint dashboard shows verification and validation rates per iteration, so you can adapt the test plan continuously.
SquashTM integrates natively with GitLab, Jira, Azure DevOps, Jenkins, GitHub Actions and the main bug trackers (Redmine, Mantis, Bugzilla, Tuleap). These integrations synchronise test data with the organisation's existing toolchain.
Trigger test plan execution from your CI/CD pipeline (Jenkins, GitLab CI, Azure DevOps…) and retrieve the results automatically in SquashTM.
Yes. Step-by-step manual execution and exploratory testing on one side; results reported from CI/CD pipelines and orchestration with SquashTM Orchestrator on the other. Both kinds coexist in the same repository, with unified reporting of results. Indicators help identify which test cases to automate first.
A sovereign solution
SquashTM is designed, developed and maintained in France by Henix. Its core is open source, and hosting and licence choices remain in your hands. You stay in control of your data: your test asset is kept whether you move from a commercial licence to the Community edition or decide to use it in another tool.
On your own infrastructure on-premise, or in France on an infrastructure maintained by Henix and hosted by Scaleway.
Authentication relies on your LDAP directories or your SSO identity provider. Permissions can be configured per project and per profile, so sensitive scopes can be kept separate.
Yes. The application is audited and certified by Ziwit, a French company specialising in cybersecurity.
Yes, at any time and with no data loss. Requirements, test cases, campaigns and results remain accessible; only the advanced features of the Premium and Ultimate editions become unavailable. The tool keeps working and the test asset remains usable — a documented exit strategy, of the kind the EU DORA regulation requires of financial entities for their critical ICT services.
Requirements, test cases, campaigns and results can be exported in Excel and XML formats, with no dependency on a service engagement or contractual lead time.
Yes. Requirements and test cases can be imported in spreadsheet format. From H1 2027, a pivot format will also make it possible to migrate a complete test asset from Xray.
Ready to structure your testing?
Download SquashTM Community for free or talk to an expert to find the right set-up for your organisation.