QA-maintained inputs

Datasets

Draft a revision, add or edit expected values, validate the immutable blob version, then publish it for runs. Published revisions cannot be edited.

Suite configuration

Add test suite

Suite key Permanent unique key using lowercase letters, numbers, and hyphens. Display name Runner type Operation type Sent as the SPADE operationType. Default document type Optional; a test case tag can override it. Comparator SPADE API URL override Optional. Leave blank to use the endpoint supplied for Local, QA, or Stage. Source Blob service URI Defines the target storage account. The harness first looks for matching fixture credentials, then uses a saved connection string or managed identity. Source Blob container Reuse Blob access settings from suite Optional fallback access configuration. It is used only when it matches the target account above. Source Blob Storage connection string Optional. Saved credentials are masked; reveal them only when editing this suite.

Default run settings Environment Copied to every new dataset revision. Parallel files Runs per file Attempt timeout (seconds) Maximum attempts per file

Data extraction quality

Critical fields are measured separately in every run. The saved list is copied into each run so historical results do not change later.

Critical fields Separate field names with commas or new lines. Matching is case-insensitive.

Fields discovered in the latest dataset

Save the suite and publish a dataset to discover fields.

Available suites

SPADE test suites

Loading suites…