Is your feature request related to a problem? Please describe. Our company uses "Design-first approach" regarding APIs so we always define OpenAPI spec before doing any coding. Because of that we are maximising benefits from having this spec, like validating data in servers, generating clients etc… You already have basic support for OpenAPI specs, but you only use routes. You don't use schema in any way.
Describe the solution you'd like When importing OpenAPI spec, not only generate test routes, but also generate JSON schema that will be used to do assertions without any user input.
Describe alternatives you've considered At least allow to define general data types for assertions :) So I could easily define "this field should be string with min-length of 2 characters" or "this should be floating point number" instead of giving exact value.
original GH issue link https://github.com/checkly/public-roadmap/issues/75
Please authenticate to join the conversation.
In Review
💡 Feature Request
API Checks
13 days ago
Tim Nolet
Get notified by email when there are changes.
In Review
💡 Feature Request
API Checks
13 days ago
Tim Nolet
Get notified by email when there are changes.