On Thu, Dec 05, 2013 at 04:34:52PM -0700, Cox, Michael wrote:
On Thu, Dec 5, 2013 at 9:28 AM, Steven Watanabe
wrote: Patches aren't the only use for attachments. Test cases are also common (and absolutely critical). If the github issue tracker doesn't support attachments, then it's simply a non-starter.
I'm assuming by the term test cases that means Boost.Test unit-tests.
A test case as in a minimal piece of end user application code that demonstrates a problem. It may be retrofitted into an actual Boost.Test testcase once there is a clear solution to it, but that's a significant burden to put on an end user that just wants to report a bug with reproduction instructions.
Wouldn't be more convenient to see the modified/new unit-tests for a library code change in the pull-request?
Convenient, sure. Practically doable by end users unfamiliar with the Boost codebase and Boost.Test? Not really. If I'm not wrong, the discussion is about end-user issues as well, not just patch requests. -- Lars Viklund | zao@acc.umu.se