Keyboard

↓ ↑
move between the rows you can see
→
open a feature, then step into it
←
close a feature, or step out to the one above
Enter
go to the page in focus
Tab
the same rows, plus everything else on the page
/
search the whole report
m
open or close the navigation drawer
Esc
leave the search box, or close the drawer
?
this list

Publishes a markdown cell in the notation you wrote it in

All 10 scenarios hold

The reporter publishes the value a row ran with, and not the text of the cell. It therefore writes every value back out, and each format writes that value back the way that format can.

Where the formats differ, the rules below show all three side by side. Markdown and AsciiDoc come first. Both are plain text, and both answer most questions alike. HTML comes last, because its answer is markup and always the longest.

A collection does not fit that shape. Markdown alone puts a whole collection inside a table cell. AsciiDoc opens a bulleted block or a description list below the cell. HTML nests list markup inside the cell. A table can hold neither of those, so the notation rule belongs to markdown alone.

Markdown writes a collection back in the notation a table uses, nested to any depth. A list takes square brackets, a set takes braces, and a map takes key: value pairs. A reader of the published spec therefore meets the value spelled the way they would spell it themselves.

Below, Cell is what a table row holds. Published cell is what the markdown report shows for that row.

expected outcome broken scenario
ScenarioCellPublished cell?
A plain valueAliceAlice
An empty list[][]
A list of values[1, 2, 3][1, 2, 3]
An empty set{}{}
A set of values{1, 2, 3}{1, 2, 3}
An empty map[:][:]
A map of values[a: 1, b: 2][a: 1, b: 2]
A list within a list[[1, 2], [a, b]][[1, 2], [a, b]]
A map within a map[a: [b: 1]][a: [b: 1]]
Collections mixed[a: [1, 2], b: {3}][a: [1, 2], b: {3}]