Skip to content

Acceptance test platform

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical ATP
Prototype reference ATP prototype (ConnectSoft.DesignPrototypes)
Managed edition SelfOperated (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Acceptance suites, environments and results live in pipelines nobody can browse; flaky tests hide regressions.

Product intent

Suites, runs, environments, results with flakiness tracking and evidence — the Factory's evaluation and pipeline patterns for a QA organization.

What the Factory makes different here: typed results and evidence records like the Factory's pipeline and evaluation services.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane QA Agent, Backend Developer Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent —
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP QA Agent, Backend Developer Agent, DevOps Agent, Observability Engineer Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test, pipeline, observability
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: testing-and-quality-assurance-workflows.

Generated product shape

C4Context
    title Acceptance test platform system context
    Person(user, "Users", "ATP users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Acceptance test platform") {
        System(ctx_Suites, "Suites", "suites, scenarios, versions")
        System(ctx_Runs, "Runs", "runs, environments, results")
        System(ctx_Quality, "Quality", "flakiness, trends, gates")
    }
    Rel(user, ctx_Suites, "uses through the product gateway GW-07")
    Rel(factory, ctx_Suites, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Suites suites, scenarios, versions SuitePublished
Runs runs, environments, results RunCompleted
Quality flakiness, trends, gates GateEvaluated

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
Worker (runners) connectsoft-microservice
QA shell connectsoft-blazor-shell
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

ATP prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Self-operated.