You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really helpful if there could be an option to display the standard out for tests. When doing Agile end-of-iteration demos, it would be great to walk through the Spock Report and then inspect the standard out which could show that data was saved to a database, json returned from a service call, etc....
The text was updated successfully, but these errors were encountered:
While I understand your request, I think this problem can already be solved with external tools.
For example, the built-in Gradle reports already include stdout output (but not the Specification's block descriptions, of course). If you have a CI, it will most likely also make the test output available easily.
In any case, because stdout is already being read from other tools, I am not sure this would even be possible. If you think this should be easy to do, feel free to submit a PR so we can discuss this in more detail.
My suggestion would be to try to use the already-generated JUnit reports (or even Gradle reports) which capture the standard output, and just add a little link to those reports from the spock-report.
Including any JS in the html reports just to show that output would be unacceptable. I really think that we should separate this information from standard reports, and that the reports should be "printable" in a sense that I don't want reports to require you to see them online as if it were a website.
It would be really helpful if there could be an option to display the standard out for tests. When doing Agile end-of-iteration demos, it would be great to walk through the Spock Report and then inspect the standard out which could show that data was saved to a database, json returned from a service call, etc....
The text was updated successfully, but these errors were encountered: