First-party product documentation. Instructions are verified against the dFlow~IQ desktop implementation. Labels appear exactly as they do in the application where practical.
Understand the test boundary
- Manual and same-cluster only.
- Timeout from 1 to 120 seconds; default 30.
- 1 to 1,000 fixtures, at most 4 MiB total.
- 1 to 100 assertions across at most 20 output topics.
- At most 10,000 observed records and 32 MiB.
- Runs and reports are not retained.
Add input fixtures
Input topicWhere the UTF-8 fixture is published.
Key (optional)Blank produces a null Kafka key.
Publish as tombstoneProduces a null value.
ValueUTF-8 fixture body.
HeadersOne name=value per line; name alone creates a null-valued header.
A keyed tombstone on a compacted topic represents deletion intent. Use it only when the scenario explicitly requires it.
Choose assertions
Exact record countPasses only when post-baseline count equals the expected number.
Key equalsAt least one new record must match the key.
Header equalsAt least one new record must contain the expected header.
JSON field equalsSupports dotted fields and numeric array indexes.
Schema validRequires Registry framing and successful decoding; JSON Schema content is also validated.
Expected absencePasses only after the full timeout without a new matching record.
Preview, confirm and run
- Save test.
- Select Preview test and review byte totals, topics, fixtures and assertions.
- Type the exact case-sensitive test name in Confirmation.
- Select Run test.
- dFlow~IQ captures output end offsets, publishes fixtures and evaluates only later records.
- Review PASS, FAIL or TIMEOUT and each assertion message.
Any edit or cancellation invalidates the preview. Save required result evidence before leaving the screen because reports are memory-only.