PUT request in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding PUT request idempotency

Which statement best describes the idempotency property of a PUT request in REST API testing?

A A PUT request always creates a new resource regardless of repetition.

B A PUT request can be repeated multiple times with the same effect as a single request.

C A PUT request cannot be repeated without causing errors.

D A PUT request is used only for retrieving data without changes.

💡 Hint

Think about what happens if you send the same update multiple times.

PUT requests are idempotent, meaning sending the same request multiple times results in the same state as sending it once.

❓ Predict Output

intermediate

Output of a PUT request test in Postman

Given this Postman test script for a PUT request, what will be the test result?

Postman

pm.test('Status code is 200', function () {
    pm.response.to.have.status(200);
});
pm.test('Response body has updated name', function () {
    var jsonData = pm.response.json();
    pm.expect(jsonData.name).to.eql('Alice');
});

A Both tests fail if the response body is empty.

B The tests pass regardless of response content.

C The first test fails if status is 200, second test always passes.

D Both tests pass if the server returns status 200 and the updated name 'Alice'.

💡 Hint

Check what each test is verifying in the response.

The first test checks the HTTP status code is 200. The second test checks the JSON response has the updated name 'Alice'. Both must be true to pass.

❓ locator

advanced

Best locator for verifying PUT request response field

In Postman test scripts, which is the best way to access the 'email' field from a JSON response after a PUT request?

A var email = pm.response.json().email;

B var email = pm.response.body.email;

C var email = pm.response.get('email');

D var email = pm.response.text().email;

💡 Hint

Consider how to parse JSON response in Postman scripts.

pm.response.json() parses the response body as JSON, allowing direct access to fields like 'email'.

❓ assertion

advanced

Correct assertion for PUT response status and content

Which Postman test assertion correctly verifies the PUT response has status 204 and an empty body?

A pm.test('Status is 204', () => pm.response.to.have.status(204)); pm.test('Body is empty', () => pm.expect(pm.response.text()).to.eql(''));

B pm.test('Status is 204', () => pm.response.to.have.status(204)); pm.test('Body is empty', () => pm.expect(pm.response.json()).to.eql({}));

C pm.test('Status is 204', () => pm.response.to.have.status(204)); pm.test('Body is empty', () => pm.expect(pm.response.body).to.be.null);

D pm.test('Status is 204', () => pm.response.to.have.status(204)); pm.test('Body is empty', () => pm.expect(pm.response.text()).to.be.null);

💡 Hint

Think about how to check an empty response body as text.

pm.response.text() returns the response body as a string. For empty body, it should equal an empty string ''.

❓ framework

expert

Automating PUT request tests with Newman CLI

You want to run a Postman collection with PUT request tests automatically in your CI pipeline using Newman. Which command correctly runs the collection and outputs a JSON report?

A newman start collection.json -r json -o report.json

B newman execute collection.json --output json report.json

C newman run collection.json -r json --reporter-json-export report.json

D newman run collection.json --json-report report.json

💡 Hint

Check Newman documentation for JSON reporter options.

The correct Newman command uses '-r json' to specify JSON reporter and '--reporter-json-export' to set output file.