Contents

Feature: Core Schema: type

  Scenario: string
    When the schema is '{ "type": "string" }'
    Then '"hello, world"' is valid JSON

  Scenario: number
    When the schema is '{ "type": "number" }'
    Then '3.14159' is valid JSON
    And '-123.41235' is valid JSON
    And '2112' is valid JSON
    But '"1234"' is not valid JSON

  Scenario: integer
    When the schema is '{ "type": "integer" }'
    Then '2112' is valid JSON
    And '-12' is valid JSON
    But '3.14159' is not valid JSON

  Scenario: boolean
    When the schema is '{ "type": "boolean" }'
    Then 'true' is valid JSON
    And 'false' is valid JSON

  Scenario: object
    When the schema is '{ "type": "object" }'
    Then this is valid JSON:
      """
      { "person": "felizberto" }
      """

  Scenario: array
    When the schema is '{ "type": "array" }'
    Then this is valid JSON:
      """
      ["foo", "bar", "baz"]
      """

  Scenario: null
    When the schema is '{ "type": "null" }'
    Then 'null' is valid JSON

  Scenario: any
    When the schema is '{ "type": "any" }'
    Then these are valid JSON:
      | "Felizberto"   |
      | 3.1415         |
      | 2112           |
      | true           |
      | { "age": 24 }  |
      | ["foo", "bar"] |
      | null           |

  Scenario: union
    When the schema is '{ "type": ["string", "number"] }'
    Then '"Felizberto"' is valid JSON
    And '2112' is valid JSON
    But 'true' is not valid JSON

  Scenario: union allowing null values
    When the schema is '{ "type": ["string", "null"] }'
    Then 'null' is valid JSON

  Scenario: union with schema element
    When the schema is:
      """
      {
          "type": [
              "string",
              { "type": "integer", "maximum": 2112 }
          ]
      }
      """
    Then '"Felizberto"' is valid JSON
    And '2112' is valid JSON
    But '2113' is not valid JSON

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
jschematic-0.1.0	features/type.feature
jschematic-0.0.9	features/type.feature