Description formatting (Markdown) in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Postman render Markdown in descriptions?

In Postman, which of the following Markdown elements will correctly render as bold text in a request description?

A **bold text**

B `bold text`

C _bold text_

D ~bold text~

💡 Hint

Think about the Markdown syntax for bold text.

In Markdown, double asterisks or double underscores make text bold. Postman supports this syntax in descriptions.

❓ Predict Output

intermediate

What is the rendered output of this Markdown in Postman description?

Given this Markdown snippet in a Postman request description:

# Header 1
Some *italic* text and a [link](https://example.com)

What will the rendered output look like?

A Header 1 as normal text, italic text as normal, and a link shown as URL only

B A large header 'Header 1', italic text 'italic', and a clickable link labeled 'link' pointing to https://example.com

C Header 1 in bold, italic text in bold, and a link that is not clickable

D Plain text showing '# Header 1', '*italic*', and '[link](https://example.com)' without formatting

💡 Hint

Markdown headers start with # and links use [text](url) syntax.

Markdown renders # Header 1 as a large header, *italic* as italic text, and [link](url) as a clickable hyperlink.

❓ assertion

advanced

Which assertion correctly checks for presence of bold text in Postman test script?

You want to write a Postman test script to verify that the response description contains bold text formatted with Markdown. Which assertion is correct?

Postman

pm.test('Description contains bold text', () => {
    const desc = pm.response.json().description;
    // Which assertion below is correct?
});

A pm.expect(desc).to.match(/\*\*.*\*\*/);

B pm.expect(desc).to.include('**');

C pm.expect(desc).to.include('<strong>');

D pm.expect(desc).to.have.property('bold');

💡 Hint

Markdown bold uses double asterisks, so a regex can detect it.

Since the description is raw Markdown, checking for ** with a regex is best. HTML tags like <strong> won't appear in raw Markdown.

🔧 Debug

advanced

Why does this Markdown not render as a list in Postman description?

This Markdown is used in a Postman request description:

- Item 1
-Item 2
 - Item 3

Why does only 'Item 1' render as a list item?

A Because the indentation before 'Item 3' is too large

B Because Postman does not support lists in descriptions

C Because '-Item 2' lacks a space after the dash, so it's not recognized as a list item

D Because the dash must be replaced with asterisk (*) for lists in Postman

💡 Hint

Markdown requires a space after the dash for list items.

In Markdown, list items must have a space after the dash. '-Item 2' is treated as normal text, so only 'Item 1' is a list item.

❓ framework

expert

How to automate validation of Markdown formatting in Postman descriptions?

You want to create an automated test framework that validates Markdown formatting in Postman request descriptions to ensure consistent style. Which approach is best?

A Write Selenium UI tests to open Postman app and visually check description rendering

B Export Postman collection and manually review descriptions for Markdown correctness

C Use Postman test scripts to parse the description text and apply regex checks for Markdown patterns

D Use a third-party Markdown linter tool integrated in CI pipeline to scan exported Postman collection JSON

💡 Hint

Think about scalable, automated validation outside Postman UI.

Exporting the collection JSON and running a Markdown linter in CI is scalable and automated. Postman test scripts can't parse descriptions before execution, and UI tests are brittle.