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 broken row's message below the table

All 6 scenarios hold

A published table carries more than its text. The reporter marks which column names the scenario, and which column holds the expectation. It also records how each row fared when it ran.

A mark needs somewhere to live, and the three formats put one in different places. HTML sets a class on the cell. AsciiDoc puts a role prefix on the value. Markdown has nowhere at all. The rules below therefore print the cell each format published, and never name the mark. A reader can then see the difference.

Each rule names the sample test class it reads. Its rows are the columns, or the rows, of that class's table.

The report lists a broken row again below the table, with the message that row failed on. A reader of the spec therefore meets what the code did, and not what the row claimed.

Every format publishes that list, each below a heading of its own and fenced its own way. The message inside is the same text in all three, which is what the format column below states.

These rows read LeapYearSample.

expected outcome broken scenario
ScenarioFormatRowMessage below the table?
A row that held
  • markdown
  • asciidoc
  • html
A year divisible by four
A row that broke
  • markdown
  • asciidoc
  • html
A century year
  • expected: "Yes"
  • but was: "No"