crunchr/openapi_conformance

A tool for validating an OpenAPI specification against an implementation.

openapi_conformance's Issues

Strategies.strings does not correctly apply min and max

The fist parameter to st.text is the alphabet that should be used, at the moment we pass **min_max. We should change this so that the first parameter to st.text is st.characters. I also think we should pass a min_codepoint=1 to ensure we don't generate text with a nul character in it.

Support for number custom formats

We a number format is supplied (see https://swagger.io/docs/specification/data-models/data-types/#numbers) then the number strategy should behave in such a way that the maximum / minimum values for the data type are respected.

Add ability to suppy custom settings to check_operation

At the moment check_operation uses given on an inner function with no way to control the settings (number of examples, health checks etc). It would be good if the user could control this externally, for example by optionally passing the arguments to the hypothesis settings decorator to OpenAPIConformance.init

Strategies.objects does not support additionalProperties

For example if we plug the following schema into Strategies.objects....

additionalProperties:
  type: int

Examples of this strategy produce empty dictionaries, whereas values such as the following should be expected:

{"hello": 32}

NOTE: The type can actually be any arbitrary schema, so we should be able to generate complex values.

Provide a function to create a django TestClient request

The example snippet in the readme is the basis for what is needed to generate a request for the django TestClient. It might be nice to wrap this up in a function (or at least an example).

Strategies.objects does not merge allOf with own schema

When you have the following schema:

    Derived:
      allOf:
        - type: object
          properties:
            baseProperty:
              type: string
      properties:
        derivedProperty:
          type: string

Strategies.objects will happily generated objects with baseProperty but properties from it's own schema (i.e. derivedProperty) will not be generated. This is because it chooses either the allOf or it's own schema for generation (i.e. for schema in schema.all_of or [schema]). This should be changed to include all_of and it's own schema.