response = client.flow_unit_tests.execute_test_suite(
flow_id="a1b2c3d4",
payload={
"test_case_ids": ["tc_001", "tc_002"],
"mock_data_matrix": {"input_var": "test_val"},
"assertion_thresholds": {"max_latency_ms": 200}
}
)
Running this on Python 3.9 with SDK v2.4.1 throws a 422 Unprocessable Entity right out of the gate. The platform documentation states “execute payloads must align with testing engine constraints and maximum test suite duration limits to prevent execution failure” but the timeout is set to sixty seconds and the job still dies.
Hitting /api/v2/flow/unit-tests/execute with an atomic POST operation keeps failing on format verification. I’m passing the exact JSON structure the schema demands, yet the automatic coverage report generation trigger never fires. The docs explicitly say “automatic coverage report generation triggers for safe execute iteration require a valid webhook callback endpoint” so I wired up a dummy CI/CD quality gate URL in the request headers. Still gets rejected.
Path traversal checking works fine in the local dev environment. The edge case simulation verification pipeline throws a schema mismatch the second the mock data matrix contains nested objects. Flattening the JSON doesn’t help. The assertion threshold directives just ignore the latency tracking fields entirely. Audit logs show the test run initiated, then immediately bails with a 504 Gateway Timeout.
The whole point is exposing a test executor for automated flow management. The Python SDK method flow_unit_tests.execute_test_suite isn’t recognizing the execution_validation_logic parameter at all. Documentation claims “synchronizing execution events with external CI/CD quality gates via webhook callbacks for alignment” happens automatically on a successful POST. It’s not syncing.
Why is the engine rejecting the payload when it matches the schema exactly? I’ve been guessing with max_latency_ms.