Mocking and test data: Boomi environment extensions per run

Testing an integration usually means not hitting the real endpoint. Weave applies Boomi environment extensions for a single test run — then restores everything:

Connections — point a connection at a mock endpoint or a sandbox instead of production.
Operations — change an operation’s fields (a path, a resource, an object type) for the run.
Process properties — swap a default value, e.g. a feature flag or a batch size.
Cross-reference tables — replace a table’s contents with test data.

Overrides live in the test view (and in the YAML test case), get applied to the Atom before the run, and are restored afterward — your Atom’s real configuration is untouched between runs.

Test data

Alongside overrides, a test seeds the process with input documents after its start shape:

multiple documents per run, with MIME types
dynamic document properties and dynamic process properties per document
inline data in the YAML, or referenced files

Combined with assertions and coverage, this makes a Boomi test repeatable: same inputs, same environment, every run — in the editor or in CI.