Task #3140
closed
Integration tests should be more verbose on error
0%
Description
stderr logs in IntegrationTests should include more information about the failure.
To discover what could have went wrong in http://gerrit.named-data.net/#/c/2392/3, I had to go into the intergration test source and infer from the line number in run.log which check failed.
Updated by Junxiao Shi about 10 years ago
- Description updated (diff)
There isn't a run.log in integ. That file in the archives I upload is a capture of stderr logs, and ndn-cxx-breaks would capture them as run.log.
The description of this issue does not contain a measurable goal, ie. it's indeterminable whether a solution fulfills the requirement.
The description shall be updated before this issue can be assigned.
Updated by Junxiao Shi almost 10 years ago
- Status changed from New to Closed
Alex agrees at 20151201 conference call that he can participate in some of integ code reviews.
This issue itself is closed because there's nothing to do here.
If Alex believes some specific test cases need improvements, add the details and reopen this issue.