JSON Schema validation in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the result of this JSON Schema validation?

Given this JSON Schema and JSON data, what will Postman report after validation?

Postman

{
  "type": "object",
  "properties": {
    "name": {"type": "string"},
    "age": {"type": "integer", "minimum": 18}
  },
  "required": ["name", "age"]
}

Data:
{
  "name": "Alice",
  "age": 17
}

A Validation fails because 'age' is less than the minimum 18.

B Validation fails because 'age' is not an integer.

C Validation passes successfully.

D Validation fails because 'name' is missing.

💡 Hint

Check the 'minimum' constraint for the 'age' property.

The schema requires 'age' to be an integer with a minimum value of 18. The data has 'age' as 17, which is below the minimum, so validation fails.

❓ assertion

intermediate

Which assertion correctly validates the JSON response schema in Postman?

You want to assert that the response JSON has a 'status' string and an 'items' array. Which Postman test script assertion is correct?

Postman

const schema = {
  type: 'object',
  properties: {
    status: { type: 'string' },
    items: { type: 'array' }
  },
  required: ['status', 'items']
};

A pm.test('Schema is valid', () => pm.response.to.have.jsonSchema('schema'));

B pm.test('Schema is valid', () => pm.response.to.have.jsonSchema(schema));

C pm.test('Schema is valid', () => pm.response.to.have.jsonSchema({}));

D pm.test('Schema is valid', () => pm.response.to.have.jsonSchema());

💡 Hint

The schema variable must be passed as an object, not a string or empty.

Option B correctly passes the schema object to the jsonSchema assertion. Other options pass invalid arguments causing errors or false positives.

🔧 Debug

advanced

Why does this JSON Schema validation fail unexpectedly?

This schema expects a property 'email' as a string with format 'email'. The data has a valid email string. Why does validation fail?

Postman

{
  "type": "object",
  "properties": {
    "email": {"type": "string", "format": "email"}
  },
  "required": ["email"]
}

Data:
{
  "email": "[e-mail]"
}

A The 'required' array is missing the 'email' property.

B The 'email' string is invalid because it lacks a domain.

C The 'format' keyword is not supported by Postman's JSON Schema validator, causing failure.

D The 'type' of 'email' should be 'email' instead of 'string'.

💡 Hint

Check Postman's support for JSON Schema format validation.

Postman's JSON Schema validator does not enforce 'format' keywords like 'email', so it may ignore them but does not cause failure. This causes unexpected validation failure only if relying on format enforcement.

🧠 Conceptual

advanced

What is the main purpose of JSON Schema validation in API testing?

Choose the best explanation for why testers use JSON Schema validation in Postman or similar tools.

A To check that the API response structure and data types match expected definitions.

B To verify the API response time is within limits.

C To ensure the API server is running without errors.

D To test the API authentication mechanism.

💡 Hint

Think about what JSON Schema describes.

JSON Schema validation checks the shape and data types of JSON responses to ensure they meet the expected contract.

❓ framework

expert

How to implement JSON Schema validation in a Postman test script for nested objects?

Given this schema with nested objects, which Postman test script correctly validates the response?

Postman

const schema = {
  type: 'object',
  properties: {
    user: {
      type: 'object',
      properties: {
        id: { type: 'integer' },
        profile: {
          type: 'object',
          properties: {
            email: { type: 'string' },
            active: { type: 'boolean' }
          },
          required: ['email', 'active']
        }
      },
      required: ['id', 'profile']
    }
  },
  required: ['user']
};

A pm.test('Nested schema validation', () => pm.response.to.have.jsonSchema(schema.required));

B pm.test('Nested schema validation', () => pm.response.to.have.jsonSchema(schema.user));

C pm.test('Nested schema validation', () => pm.response.to.have.jsonSchema(schema.properties.user));

D pm.test('Nested schema validation', () => pm.response.to.have.jsonSchema(schema));

💡 Hint

Pass the full schema object to the assertion, not parts of it.

The jsonSchema assertion expects the full schema object. Passing nested parts will cause validation errors or incorrect checks.