You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customize the severity level of validation checks for status codes, schemas, and content types. Setting the severity level is useful when:
92
+
93
+
- You're actively developing your API and want to temporarily relax validation.
94
+
- You're testing new API behavior that doesn't match the current schema.
95
+
- You've encountered known issues that shouldn't block test execution.
96
+
- You want to treat certain validation failures as warnings instead of errors.
97
+
98
+
The following checks can be configured:
99
+
100
+
-`STATUS_CODE_CHECK`: Verifies if the status code returned with API responses matches the statuses described in the provided OpenAPI description.
101
+
-`SCHEMA_CHECK`: Verifies if the response body schema matches what is defined in the provided OpenAPI description.
102
+
-`SUCCESS_CRITERIA_CHECK`: Verifies if the success criteria defined in the provided Arazzo description has been met.
103
+
-`CONTENT_TYPE_CHECK`: Verifies if the `Content-Type` matches what is defined in the provided OpenAPI description.
104
+
105
+
The following severity values are available:
106
+
107
+
-`error`: Validation failures cause the workflow to fail.
108
+
-`warn`: Validation failures appear as warnings but don't fail the workflow.
109
+
-`off`: Validation checks still run, but their results are ignored.
110
+
111
+
{% admonition type="info" %}
112
+
Setting the severity of a check to `off` does not prevent the check from executing - it only prevents the check's results from affecting the workflow outcome.
113
+
{% /admonition %}
114
+
115
+
For example, the following command sets status code errors to the warning severity level:
0 commit comments