Testing before production

Testing reduces the risk of failed runs and bad data reaching downstream systems.

Test contracts with sample files

Upload representative sample files to the contract tester. Include files with valid rows, known errors, edge cases, and empty files. Adjust the rules until the contract catches the right problems.

Test pipelines manually first

After creating a pipeline, run it once on demand before enabling the schedule. Confirm that:

• The source is reachable.
• The contract validates the file as expected.
• The delivery destination receives the file.

Test standardizers with a recent run

Run the standardizer against a recent successful pipeline run. Inspect the output columns, data types, and lookup results.

Use small samples

Start with small files when testing. This makes it easier to spot issues and reduces the cost of mistakes.

Validate end-to-end

After each component works on its own, run the full flow: source → contract → pipeline → standardizer → destination.

Keep a sandbox

If possible, use a separate account or environment for development and testing. Move configurations to production only after they pass tests.