Skip to content

Commit 3e3d108

Browse files
authored
Update README.md
1 parent 00d8171 commit 3e3d108

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ Here are two aspects of contract testing: Validation and Coverage
140140

141141
### Validation
142142

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.
144144

145145
### Coverage
146146

@@ -149,7 +149,8 @@ To make sure your _whole_ API description is implemented, openapi_first ships wi
149149
> [!NOTE]
150150
> This is a brand new feature. ✨ Your feedback is very welcome.
151151
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):
153154

154155
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.
155156
```ruby

0 commit comments

Comments
 (0)