Partner / White-label
Partners can integrate QualityMax testing workflows into another product or delivery process. Start with a concrete workflow and the relevant API contract; an API integration does not by itself provide a complete branded deployment.
Choose an integration path
Section titled “Choose an integration path”| Need | Starting point |
|---|---|
| Connect a coding agent to a QualityMax workspace | Hosted MCP quickstart |
| Trigger tests in an existing CI workflow | QualityMax GitHub Action |
| Connect workflow automation | QualityMax n8n nodes |
| Build a product integration around jobs and artifacts | Partner API access and its versioned endpoint contract, agreed with QualityMax |
| Explore a dedicated deployment | Deployment options and Sovereign private preview |
The partner API covers workflows including test-case creation and generation, repository import, API-test generation, gap analysis, job reports, and execution artifacts such as screenshots, videos, and logs. Confirm which operations are enabled for your integration before promising them to customers.
Design the customer workflow
Section titled “Design the customer workflow”- Agree account, team, organization, and project ownership with QualityMax.
- Establish the authentication and authorization contract for the integrating service. Keep privileged credentials on the server.
- Submit a bounded test or generation request and retain its job identifier.
- Follow the documented completion contract. A request accepted for processing is not a completed test result.
- Display the result and available evidence in the customer’s context, with useful failure and retry states.
- Agree webhook events, delivery handling, limits, and support expectations before relying on them in production.
Use the core concepts to map projects, test cases, scripts, executions, and evidence into your product. See Evidence & Trust for what artifacts and signed records can establish.
Plan white-label requirements explicitly
Section titled “Plan white-label requirements explicitly”Contact QualityMax to agree branding, custom domains, customer isolation, deployment eligibility, commercial terms, and operational ownership. Do not assume that branding controls, a dedicated environment, or a particular service level are included with ordinary API access.
Sovereign deployments remain a private preview for design partners. The deployment page describes the current scope; this page is an integration planning guide, not a generally available self-hosting installation recipe.