Replies: 4 comments
-
That's a nice idea!
Maybe raise an error optionally like:
Do you want to keep the |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hey. There is "coverage" branch with something working, finally. Check it out. Any feedback on this would be greatly appreciated: https://github.com/ahx/openapi_first/tree/coverage?tab=readme-ov-file#test-coverage TODOs:
|
Beta Was this translation helpful? Give feedback.
-
This feature was release in 2.3.0 ✅ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Here test coverage means that the gem should be able to track and report which requests and reponses of an API description have been called during a test run.
The more request and response definitions have been called the better.
This would unaware about JSON Schema and it's branches like
if/else
,oneOf
,anyOf
,type: […]
or the like, but only care about paths, response statuses and content-types.Configuration could work like this:
Then you just run your tests and it will track all calls
RuntimeRequest#validate
andRuntimeResponse#validate
. So this will just work either if you are using the built in middlewares (which you should) or roll your own.Questions:
OpenapiFirst::Test::Coverage
orOpenapiFirst::Coverage
?Beta Was this translation helpful? Give feedback.
All reactions