<br><div><span class="gmail_quote">On 3/27/06, <b class="gmail_sendername">Andreas Raab</b> <<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It's 8MB a pop so no, I think it's not really feasible to stick that<br>test data into a method ;-)<br><br></blockquote></div><br>
<p class="MsoNormal">A test that needs 8mb of data doesn't look like a unit test
to me.<br>Why you need 8mb, you can't test the same with a few bytes
only?</p>
<p class="MsoNormal">I think that the problem is that some times is very useful
to use the assertion framework and the test runner to make another kind of
tests ("user story tests", "stress test", etc). But the SUnit framework depends
on classification to detect all test cases available (unit tests or not).<br>When I run all the unit tests on the system, I expect unit
tests, that is small and fast tests.</p>
<p class="MsoNormal">Maybe we can have a Test trait or something like that to
reuse the assertion framework, and the test runners, and keep the TestCase
hierarchy as a classification for unit tests.</p>