Nested object assertions in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a nested object assertion in Postman tests?

It is a way to check values inside objects that are inside other objects in the response JSON. This helps verify deep data structures.

beginner

How do you access a nested property in Postman test scripts?

Use dot notation like response.data.user.name or bracket notation like response['data']['user']['name'].

beginner

Example: How to assert that response.data.user.age equals 30 in Postman?

Use pm.expect(response.data.user.age).to.eql(30); inside the test script.

intermediate

Why is it important to check nested objects in API testing?

Because APIs often return complex data. Checking nested objects ensures all parts of the response are correct, not just the top level.

intermediate

What happens if you try to assert a nested property that does not exist in Postman?

The test will fail with an error or undefined value. It's good to check if the property exists before asserting.

In Postman, how do you assert that response.user.address.city equals 'Paris'?

A pm.expect(response.user.address.city).to.eql('Paris');

B Both A and B

C pm.expect(response['user']['address']['city']).to.eql('Paris');

D pm.assert(response.user.address.city == 'Paris');

Both dot notation and bracket notation work for accessing nested properties in Postman assertions.

What does pm.expect(response.data.items[0].id).to.exist; check?

A That the first item has an id property

B That the id equals zero

C That items array is empty

D That response.data is undefined

The assertion checks if the id property exists on the first item in the items array.

If response.data.user is undefined, what happens when you try pm.expect(response.data.user.name).to.eql('John');?

A Test fails with an error

B Test passes

C Test ignores the assertion

D Test logs a warning but passes

Trying to access a property of undefined causes an error and the test fails.

Which method helps avoid errors when asserting nested properties that might not exist?

A Using try-catch blocks in Postman tests

B Ignoring errors

C Both C and D

D Using optional chaining like response?.data?.user?.name

Optional chaining and try-catch blocks help safely access nested properties and handle errors.

What is the best practice for asserting nested objects in Postman?

A Assert only top-level properties

B Avoid nested assertions

C Assert nested properties directly without checks

D Check existence before asserting nested properties

Checking if nested properties exist before asserting prevents errors and makes tests more reliable.

Explain how to write assertions for nested objects in Postman test scripts.

Think about how you access deep data in JavaScript objects.

Describe common errors when asserting nested objects and how to prevent them in Postman.

Consider what happens if a nested object is missing.