Automation asset workspace
Automation is the library and composition area for saved testing assets. It does not replace Craftsman or OpenAPI TestGen; it receives their outputs and turns them into reusable runs, flows, browser coverage, and deployable exports.
What you can do
- Maintain reusable Fragments and protocol-specific REST, SOAP, and GraphQL specifications.
- Validate response documents with attachment assertions, hashes, fingerprints, and optional excluded sections or chunks.
- Inspect recorded UI macros and combine API or browser assets into ordered flows.
- Generate portable ATF projects from an explicit selection of saved specs and flows.
Starts with
- Saved fragments, specifications, browser macros, and flows created manually or by generators.
- Expected document hashes or fingerprints, response sources, and optional exclusions for document assertions.
- An explicit asset selection and runtime configuration when producing an ATF project.
Produces
- Versioned, runnable test assets and mixed end-to-end flows.
- Document assertion results with hash, fingerprint, and change metadata; response document bytes are not persisted by SpecTestEngine.
- Portable source projects for CI or external execution through ATF Export.
Use it when
- Use Automation after exploratory work has become stable enough to save and run repeatedly.
- Use document assertions to detect whether generated reports, invoices, exports, or service attachments changed without retaining their response contents.
- Open a dedicated asset page below when you need protocol-specific behavior or export details.
- Automation
- test assets
- specifications
- document assertions
- attachment assertions
- UI macros
- ATF export