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
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,7 @@ Here are two aspects of contract testing: Validation and Coverage
140
140
141
141
### Validation
142
142
143
-
By validating requests and responses, you can avoid that your API implementation processes requests or returns responses that don't match your API description. You can use [test assertions](#test-assertions) or [rack middlewares](#rack-middlewares) to validate requests and responses with openapi_first.
143
+
By validating requests and responses, you can avoid that your API implementation processes requests or returns responses that don't match your API description. You can use [test assertions](#test-assertions) or [rack middlewares](#rack-middlewares)or manual validation to validate requests and responses with openapi_first.
144
144
145
145
### Coverage
146
146
@@ -149,7 +149,8 @@ To make sure your _whole_ API description is implemented, openapi_first ships wi
149
149
> [!NOTE]
150
150
> This is a brand new feature. ✨ Your feedback is very welcome.
151
151
152
-
This feature tracks all requests/resposes that are validated via openapi_first and returns overal coverage value. Here is how to set it up with rack-test or Rails' request specs:
152
+
This feature tracks all requests/resposes that are validated via openapi_first and tells you about which request/responses are missing.
153
+
Here is how to set it up with [rack-test](https://github.com/rack/rack-test):
153
154
154
155
1. Register all OpenAPI documents to track coverage for. This should go at the top of your test helper file before loading your application code.
0 commit comments