Dynamic assertion values in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are dynamic assertion values in Postman tests?

Dynamic assertion values are test checks that use data from the response or environment variables to verify results, instead of fixed values.

beginner

Why use dynamic assertion values instead of static ones?

Because API responses can change, dynamic values make tests flexible and reliable by adapting to actual response data or variables.

intermediate

Example: How to assert a response field matches an environment variable in Postman?

Use pm.expect(responseJson.field).to.eql(pm.environment.get('variableName')) to compare the response field with the environment variable.

beginner

What Postman method helps parse JSON response for dynamic assertions?

pm.response.json() parses the response body as JSON so you can access fields for assertions.

advanced

How can you assert that a response timestamp is recent using dynamic values?

Compare the response timestamp with the current time using JavaScript Date objects inside the test script.

Which Postman function retrieves an environment variable for dynamic assertions?

A pm.variables.set()

B pm.response.json()

C pm.environment.get()

D pm.request.url()

pm.environment.get() fetches the value of an environment variable for use in assertions.

What does pm.response.json() do in Postman tests?

A Sends a JSON request

B Parses the response body as JSON

C Sets an environment variable

D Validates the response status code

pm.response.json() parses the response body so you can access its fields for assertions.

Why are dynamic assertion values important in API testing?

A They allow tests to adapt to changing response data

B They make tests faster

C They reduce the number of tests needed

D They eliminate the need for environment variables

Dynamic values let tests check actual response data, making tests flexible and accurate.

How do you compare a response field to an environment variable in Postman?

A pm.expect(response.field).to.eql(pm.environment.get('variable'))

B pm.expect(response).to.eql(variable)

C pm.environment.set('variable', response.field)

D pm.response.to.have.variable('field')

This syntax compares the response field value with the environment variable value.

Which of these is NOT a good use of dynamic assertion values?

A Checking if a user ID matches an environment variable

B Verifying a timestamp is within the last minute

C Comparing a response message to a variable message

D Asserting a fixed status code like 200

Asserting fixed status codes is static, not dynamic; dynamic assertions use changing data.

Explain how to write a dynamic assertion in Postman that compares a response value to an environment variable.

Think about how to access response data and environment variables in Postman scripts.

Describe why dynamic assertion values improve API test reliability.

Consider what happens if the API returns different data each time.

Practice

1. What is the main purpose of using dynamic assertion values in Postman tests?

easy

A. To make tests flexible by comparing values that change each time

B. To hardcode fixed values for all test runs

C. To disable assertions temporarily

D. To speed up test execution by skipping checks

Solution

1. Step 1: Understand dynamic assertion values

   Dynamic assertion values allow tests to compare values that can change between API calls, making tests adaptable.

2. Step 2: Identify the purpose in Postman

   Using dynamic values helps verify API responses that return different data each time, ensuring tests remain valid.

3. Final Answer:

   To make tests flexible by comparing values that change each time -> Option A

4. Quick Check:

   Dynamic assertions = flexible tests [OK]

Hint: Dynamic values adapt tests to changing data [OK]

Common Mistakes:

• Thinking dynamic means disabling assertions
• Confusing dynamic with fixed values
• Assuming dynamic values speed up tests

2. Which of the following is the correct way to use a Postman variable in an assertion to check a response value dynamically?

easy

A. pm.expect(pm.response.json().data.id).to.eql('{{$randomId}}');

B. pm.expect(pm.response.json().data.id).to.eql(pm.variables.get('randomId'));

C. pm.expect(pm.response.json().data.id).to.eql('$randomId');

D. pm.expect(pm.response.json().data.id).to.eql(randomId);

Solution

1. Step 1: Recall Postman variable syntax in scripts

   In test scripts, variables are accessed using pm.variables.get('variableName').

2. Step 2: Identify correct assertion usage

   pm.expect(pm.response.json().data.id).to.eql(pm.variables.get('randomId')); correctly uses pm.variables.get('randomId') to get the variable value for comparison.

3. Final Answer:

   pm.expect(pm.response.json().data.id).to.eql(pm.variables.get('randomId')); -> Option B

4. Quick Check:

   Use pm.variables.get() for dynamic values [OK]

Hint: Use pm.variables.get('name') to access variables in tests [OK]

Common Mistakes:

• Using {{}} inside test scripts instead of pm.variables.get()
• Using variable name as plain string without get()
• Assuming $variable syntax works in scripts

3. Given this Postman test snippet:

pm.test('Check user ID', () => {
  const expectedId = pm.variables.get('userId');
  pm.expect(pm.response.json().id).to.eql(expectedId);
});

If the variable userId is set to 123 and the response JSON is {"id": 124}, what will be the test result?

medium

A. Test passes because values are close

B. Test throws syntax error

C. Test fails because 124 != 123

D. Test is skipped due to missing variable

Solution

1. Step 1: Compare expected and actual values

   The expected value from variable userId is 123, but response JSON has id 124.

2. Step 2: Evaluate assertion outcome

   The assertion to.eql(123) vs actual 124 will fail because they are not equal.

3. Final Answer:

   Test fails because 124 != 123 -> Option C

4. Quick Check:

   Mismatch values cause test failure [OK]

Hint: Check exact values in assertions to predict pass/fail [OK]

Common Mistakes:

• Assuming close numbers pass equality
• Confusing syntax error with assertion failure
• Ignoring variable value in test

4. You wrote this Postman test:

pm.test('Check token', () => {
  const token = pm.variables.get('authToken');
  pm.expect(pm.response.json().token).to.eql(token);
});

But the test always fails even though the token looks correct. What is the most likely cause?

medium

A. The variable authToken is not set or is empty

B. The response JSON does not contain a token field

C. The assertion syntax is invalid

D. Postman does not support dynamic assertions

Solution

1. Step 1: Check variable usage

   If authToken is missing or empty, pm.variables.get('authToken') returns undefined or empty string.

2. Step 2: Understand assertion failure

   Comparing response token to undefined or empty string causes assertion to fail even if response token is correct.

3. Final Answer:

   The variable authToken is not set or is empty -> Option A

4. Quick Check:

   Unset variables cause assertion mismatches [OK]

Hint: Always verify variables are set before assertions [OK]

Common Mistakes:

• Assuming syntax error without checking variables
• Ignoring missing response fields
• Believing Postman lacks dynamic assertion support

5. You want to test an API that returns a new order ID each time. You store the previous order ID in a variable prevOrderId. Which Postman test code correctly asserts that the new order ID is different from the previous one?

hard

A. pm.expect(pm.response.json().orderId).to.eql(pm.variables.get('prevOrderId'));

B. pm.expect(pm.response.json().orderId).to.be.lessThan(pm.variables.get('prevOrderId'));

C. pm.expect(pm.response.json().orderId).to.be.greaterThan(pm.variables.get('prevOrderId'));

D. pm.expect(pm.response.json().orderId).not.eql(pm.variables.get('prevOrderId'));

Solution

1. Step 1: Understand the requirement

   The test should confirm the new order ID is different from the previous one, so equality must fail.

2. Step 2: Choose correct assertion

   pm.expect(pm.response.json().orderId).not.eql(pm.variables.get('prevOrderId')); uses not.eql to assert the new ID is not equal to the previous ID, matching the requirement.

3. Final Answer:

   pm.expect(pm.response.json().orderId).not.eql(pm.variables.get('prevOrderId')); -> Option D

4. Quick Check:

   Use not.eql to assert values differ [OK]

Hint: Use not.eql to check values are different [OK]

Common Mistakes:

• Using eql to check difference (wrong)
• Assuming greaterThan always works for IDs
• Confusing lessThan with difference check