Test Management as a Service

The Audit establishes where your test management stands today. We review the available documentation on requirements, systems and interfaces, map current test responsibilities and identify gaps between them. You receive a condensed test plan, risk heat map, prioritised test backlog and one-page management report. The Audit assesses the current position; it does not yet build the full test-management function. That happens in the Sprint. The Audit is completed within five working days with limited demand on your calendar. The fee is credited in full against a subsequent Sprint.

The Sprint is the core engagement. It turns the risk profile into a complete test-management model: test strategy, end-to-end scenarios across systems, processes and providers, a requirements traceability matrix, clear responsibilities, entry and exit criteria and a reporting model. Qelivia defines the authoring standard and provides fully worked sample test cases. Your team creates the bulk of the detailed test cases and steps in its own tool, because that is where the deepest system knowledge sits. Qelivia reviews and signs off the catalogue and prepares the management report with the service-readiness recommendation, residual risks and conditions. Test execution remains with your teams and providers.

Care provides ongoing test management for services already in operation. We keep the strategy and regression and integration scope current, coordinate testing across teams and providers, consolidate results and maintain the reporting needed for each release. Your teams continue to execute the tests; Qelivia maintains the management layer above them.

You get the management layer above your testing, externally and with a scope agreed in advance, instead of building up your own test management function. Qelivia assesses the risks, designs the test strategy and the end-to-end scenarios, coordinates the teams and providers involved and delivers a well-founded recommendation on service readiness, in clearly defined packages with a fixed fee. Your teams test. Qelivia orchestrates.

Yes, that is exactly the point. We manage testing for end-to-end processes, system integrations and service flows across several systems and providers, not just for individual software components. You get a risk profile covering the entire chain instead of many green individual results with no overall conclusion. The tests themselves are run by your teams, in your own tool or in the Qelivia Test Runner.

We agree scope, timeline and fee before work begins and confirm them in writing. The cost of an engagement depends on the system landscape, the number of parties involved and the timeline, so we do not publish list prices. If the scope changes later, we agree the revised basis before additional work begins.

No. Where a tool is already in place, we connect to it and work in it. Where there is none, we provide the Qelivia Test Runner for the duration of the project, so that execution, status and evidence come together in one place. The Test Runner is not a standalone product; it is the working environment through which test execution, status and evidence become visible to everyone involved. Results are handed over in your format.

No. Qelivia replaces neither your testers nor your providers. We work one level above: test strategy, scope, end-to-end scenarios, assignment of testing responsibility, coordination, risk and progress management, and the consolidated assessment at the end. Your teams carry on testing what they know best.

As a rule within three to five working days of receiving your documentation. The audit itself is completed after five working days.

Our work is aligned with ISTQB terminology and established testing practices, and it follows the ISTQB test process: test planning, test monitoring and control, test analysis, test design, test implementation, test execution and test completion. On top of that come consistent terminology, defined entry and exit criteria and a transparent, risk-based prioritisation. That makes the results auditable and ready to hand over.

By invoice once the work has been delivered, payable by bank transfer. All fees are net and subject to statutory VAT; as a business, you can normally reclaim the VAT as input tax.

We work with your existing project and requirements documentation, and only with what is genuinely needed, ideally anonymised. An NDA is in place before we start. Processing takes place within the EU in line with the GDPR, using carefully selected processors (including our hosting provider); data is neither passed on nor sold to third parties. Where we use AI-assisted tools, we do so exclusively with anonymised data. Once the project ends, copies are deleted with a record of the deletion.

Test cases, the requirements traceability matrix and the test backlog are delivered as structured Excel or CSV files that can be imported directly into Jira (including Xray and Zephyr), Azure DevOps or other test management tools. On request, we support the import together with your team, so that the results end up where your people already work. If you do not use such a tool, we provide the Qelivia Test Runner for the duration of the project: a hosted, GDPR-compliant test environment in the EU in which your teams run the test cases and in which status and evidence come together in one place for everyone involved.

We do it together, and deliberately so. Qelivia provides the test strategy, the test scenarios, the authoring standard and fully worked sample test cases including test steps, along with an enablement session and, at the end, the review and sign-off of the completed catalogue. The bulk of the test cases and steps is written by your team directly in your own tool, following that standard. The reason is a professional one: the detailed system- and tool-specific knowledge sits with you. This produces tool-native, maintainable tests rather than external artefacts, and testing capability stays in house. It requires a named, qualified person from design or development with committed time. The price and duration of the Sprint are unaffected.

Yes, where the basis supports it. Given clear requirements and reliable service, process and system documentation, we develop test cases and end-to-end service scenarios: during the Sprint, together with your team and to our authoring standard. Where that basis is missing, establishing the test basis is the first step, not writing test cases. Test execution is in every case carried out by the responsible business, technology or provider teams.

When you are looking for additional testing capacity. We do not supply testers, we do not provide contract staff and we do not operate as a test factory. Pure test automation development, penetration testing and isolated operational business testing are likewise outside our scope. There are good providers for that; it is simply a different problem from the one we solve.

Around two to four hours in total across the five working days: a kick-off (about 45 minutes), consolidated queries during the analysis (about 30 to 60 minutes) and the presentation of results (about 60 minutes). Everything else we handle using your existing documentation, without workshops and without tying up your team.