Why visual workflows simplify complex testing in Postman - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a new Postman collection run.

Postman

pm.collection.run({ [1]: '{{collectionId}}' });

Drag options to blanks, or click blank then click option'

AcollectionId

Bstart

Cexecute

DrunCollection

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names instead of collection identifier.

The collectionId is required to specify which collection to run in Postman.

2fill in blank

medium

Complete the code to add a test script that checks response status is 200.

Postman

pm.test('Status code is 200', function () { pm.response.to.have.status([1]); });

Drag options to blanks, or click blank then click option'

A201

B200

C404

D500

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong status codes like 404 or 500.

The test checks if the response status code is 200, which means success.

3fill in blank

hard

Fix the error in the test script to correctly check if response body contains 'success'.

Postman

pm.test('Body contains success', function () { pm.expect(pm.response.text()).to.[1]('success'); });

Drag options to blanks, or click blank then click option'

Acontain

Bcontains

Cincludes

Dinclude

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular or incorrect method names causing errors.

The correct Chai assertion method is include to check substring presence.

4fill in blank

hard

Fill both blanks to create a visual workflow that runs tests only if response status is 200.

Postman

if (pm.response.status === [1]) { pm.test('Run tests', function () { pm.expect(pm.response.[2]).to.be.ok; }); }

Drag options to blanks, or click blank then click option'

A200

Bjson

Ctext

D404

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong status codes or response properties.

The workflow checks if status is 200 and then tests if the JSON response is okay.

5fill in blank

hard

Fill all three blanks to create a test that checks if response JSON has a key 'status' with value 'success'.

Postman

pm.test('Status key is success', function () { const jsonData = pm.response.[1](); pm.expect(jsonData.[2]).to.eql([3]); });

Drag options to blanks, or click blank then click option'

Ajson

Bstatus

C'success'

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'text' instead of 'json', wrong key names, or missing quotes around string.

This test parses the response as JSON, then checks if the 'status' key equals the string 'success'.

Practice

1. Why do visual workflows make complex testing easier in Postman?

easy

A. They replace the need for any manual testing

B. They automatically fix all test errors

C. They show each test step clearly and in order

D. They run tests faster than code scripts

Solution

1. Step 1: Understand visual workflows

   Visual workflows display test steps as blocks or nodes, making the process clear and easy to follow.

2. Step 2: Identify how clarity helps testing

   Clear step-by-step visuals reduce confusion and help testers understand complex flows better.

3. Final Answer:

   They show each test step clearly and in order -> Option C

4. Quick Check:

   Clear steps = easier testing [OK]

Hint: Visual means clear steps shown [OK]

Common Mistakes:

• Thinking visual workflows fix errors automatically
• Believing visual workflows replace manual testing
• Assuming visual workflows speed up test execution

2. Which of the following is the correct way to represent a visual workflow step in Postman?

easy

A. A block or node connected by arrows showing flow

B. A plain text list of test steps

C. sendRequest() function call in code

D. A spreadsheet with test data only

Solution

1. Step 1: Identify visual workflow elements

   Visual workflows use blocks or nodes connected by arrows to show the order and relationship of steps.

2. Step 2: Compare options

   Only A block or node connected by arrows showing flow describes a visual, graphical representation suitable for workflows.

3. Final Answer:

   A block or node connected by arrows showing flow -> Option A

4. Quick Check:

   Visual = blocks and arrows [OK]

Hint: Visual means blocks connected by arrows [OK]

Common Mistakes:

• Confusing code calls with visual steps
• Thinking plain text lists are visual workflows
• Using spreadsheets as workflow visuals

3. Consider a Postman visual workflow with three steps: A sends a request, B validates response, C logs results. If step B fails, what happens next?

medium

A. Step C runs regardless of step B's result

B. Step C is skipped because step B failed

C. The workflow restarts from step A automatically

D. Step B retries until it passes before step C

Solution

1. Step 1: Understand workflow step dependencies

   In visual workflows, steps usually depend on the success of previous steps to continue.

2. Step 2: Analyze failure impact

   If step B (validation) fails, the next step C (logging results) is typically skipped to avoid incorrect logging.

3. Final Answer:

   Step C is skipped because step B failed -> Option B

4. Quick Check:

   Fail step stops next step [OK]

Hint: Failed step usually stops next steps [OK]

Common Mistakes:

• Assuming all steps run regardless of failures
• Thinking workflow restarts automatically on failure
• Believing failed steps retry endlessly

4. You created a visual workflow in Postman but the test steps run out of order. What is the most likely cause?

medium

A. The workflow has too many steps to run

B. The test data is missing from the requests

C. The Postman app is outdated and needs update

D. Steps are not connected properly with arrows

Solution

1. Step 1: Check workflow connections

   Visual workflows rely on arrows or connectors to define the order of steps.

2. Step 2: Identify cause of unordered execution

   If steps run out of order, it usually means the arrows linking steps are missing or incorrect.

3. Final Answer:

   Steps are not connected properly with arrows -> Option D

4. Quick Check:

   Missing arrows = wrong order [OK]

Hint: Check arrows connect steps correctly [OK]

Common Mistakes:

• Blaming missing test data for order issues
• Assuming app version causes step order
• Thinking too many steps cause disorder

5. You want to create a visual workflow in Postman that tests multiple API endpoints with shared setup steps and different validations. How does using visual workflows simplify this complex testing?

hard

A. By allowing reuse of setup steps and branching validations visually

B. By automatically generating test code for all endpoints

C. By running all tests in parallel without configuration

D. By hiding complex steps so testers see only results

Solution

1. Step 1: Understand reuse and branching in visual workflows

   Visual workflows let you create shared setup steps once, then branch into different validations for each endpoint.

2. Step 2: Identify how this simplifies complex testing

   This reduces duplication, makes the flow clear, and helps manage multiple test paths easily.

3. Final Answer:

   By allowing reuse of setup steps and branching validations visually -> Option A

4. Quick Check:

   Reuse and branching simplify complex tests [OK]

Hint: Visual reuse and branches simplify tests [OK]

Common Mistakes:

• Expecting automatic code generation from visuals
• Thinking tests run parallel without setup
• Believing visuals hide steps instead of showing them