From 40a53d36d3a42c0807476d0c0cfd8f3abf0f8418 Mon Sep 17 00:00:00 2001 From: Michael Pursifull Date: Wed, 4 Feb 2026 14:33:02 -0600 Subject: [PATCH] test: add fixture for non-string variable value Adds test coverage for the case where a YAML number value appears in the variables record (e.g., `count: 5`). YAML parses unquoted numbers as integers, which the schema correctly rejects as invalid_type (expected string, received number). This is a likely contributor mistake worth covering. 28/28 fixtures now passing. --- .../invalid/bad-variables-type.workflow.yaml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 test/fixtures/workflow-schema/invalid/bad-variables-type.workflow.yaml diff --git a/test/fixtures/workflow-schema/invalid/bad-variables-type.workflow.yaml b/test/fixtures/workflow-schema/invalid/bad-variables-type.workflow.yaml new file mode 100644 index 000000000..a01b1f3b5 --- /dev/null +++ b/test/fixtures/workflow-schema/invalid/bad-variables-type.workflow.yaml @@ -0,0 +1,14 @@ +# Expected: FAIL +# Error code: invalid_type +# Error path: variables.count +# Error expected: string +# Error received: number +# Tests: variables with non-string value (YAML number) produces wrong_type error +name: bad-variables-type-test +description: "A workflow with non-string variable value" +author: "Test" +standalone: true +web_bundle: false +variables: + valid_key: "string value" + count: 5