Handling Detailed Output from Unit Tests about ci HOT 3 CLOSED

All good questions. I think that we should limit output that is posted to the server. If there are differences, maybe we should post "diffs" if they are less than 1MB or something. Maybe just the summaries are enough. If there is anything amiss, then we are going to look into it. Not sure that there will be too much utility in having everything posted to the server in that case.

So as I'm writing and thinking, I think concise summaries are enough to post to the server. If everything passes, that's all we need to know probably. If not, having a bunch of information posted won't really help much, because we are going to go back and look in the tests and poke around...

from ci.

Andrew and I had a conversation and came up with the same conclusion. We will limit the unit testing details to be a summary less than 1MB. The person designing the unit tests should analyze the output from their software and create a summarized version with the most important points. If there is a problem, the developer will probably start playing with the software and running the unit tests by hand at that point.

Thank-you for your input.

from ci.

Loving this new workflow! (Using github to track/comment/etc)

from ci.