cucumber/cucumber-html — Issue #12: Missing stack trace within the HTML output for steps that are in error
Author: restagner
Created: 2012-02-07 17:32:28+00:00
State: open

If the test run encounters an error, the resulting HTML file generated formats the step correctly (i.e., red color for failed step), however, I'm not seeing a stack trace of the error as I use to see in Cuke4Duke.

NOTE: I am seeing the error message, as it appears on the command-line, within the report.js file. It looks like

```
formatter.result({
"duration": 13452758,
"status": "failed",
"error_message": "junit.framework.ComparisonFailure: expected:\u003c[Cookies]\u003e but was:\u003c[Google]\u003e\n\tat junit.framework.Assert.assertEquals(Assert.java:85)\n\tat junit.framework.Assert.assertEquals(Assert.java:91)\n\tat org.stag.hello.StepDefs.thePageTitleReturnedShouldBe(StepDefs.java:92)\n\tat âœ½.Then the page title returned should be \"Cookies\"(cheese.feature:8)\n"
});
```

It would be helpful to embed the stack trace within the index.html file for each of the failed steps.