Test Orchestration · Engineering Tooling
Testorch
A test-orchestration integration used in Factory's engineering workflow.
Overview
Testorch appears in the Factory repository as a test-orchestration integration rather than a standalone Simorgh product. The configuration enables Django, React, and security profiles, writes output to a structured directory, and is referenced by the Factory testing workflow.
The tool itself is external. Simorgh's work is the integration and the engineering discipline of running repeatable checks as part of software production.
Origin and motivation
Factory's validation thesis depends on executable checks. Testorch is one of the tools used to organize those checks and preserve their output.
The problem
A multi-surface engineering workflow needs a consistent way to run different test profiles and retain evidence, rather than relying on ad hoc local commands.
Who it is for
Factory engineers and future platform users who need repeatable test orchestration across backend, frontend, and security surfaces.
Vision and objectives
A governed validation workflow where test profiles, output, and acceptance evidence are part of the engineering record.
Key capabilities
- Django test profile (configured)
- React test profile (configured)
- Security profile (configured)
- Structured output directory
- Integration with Factory's validation workflow
Engineering and architecture
The available evidence is the Factory configuration, ignore file, and test output log. No Testorch source implementation is present in the Simorgh repositories, and no public Testorch product is claimed.
Difficult problems and solutions
Attribution boundary
Testorch is an external tool. Simorgh's contribution is the integration and the surrounding validation process, not the orchestration engine itself.
Current status
Testorch is a tooling integration, not a standalone product or commercial platform. It is included in the portfolio to document the engineering toolchain accurately.
Discuss Testorch
If this work is relevant to your organization, start with the problem and the context.