On Oct 3, 2004, at 8:06 PM, Avi Bryant wrote:
On Oct 3, 2004, at 7:57 PM, Doug Way wrote:
On Sep 24, 2004, at 3:12 PM, stéphane ducasse wrote:
I'm creating some tests for the decompiler (inspired by the one in SystemDictionary) and they are realllllly slow. So I'm thinking to create some kinds of SlowTestCase that could be turned off/on on demand. But I would like to know if someone already proposed a solution to that problem.
I think this is pretty common with unit tests... we had a similar situation where I used to work. I think we ended up just having a different test suite for the slow tests, and they were run nightly, instead of being run whenever you checked in code. But having a SlowTestCase class might be an okay way to handle it too.
And on the flip side, it might be nice to have a QuickTestCase too, that can be run all the time - like, every time you accept a method...
Hey, neat idea ... I got to put that on my todo list for BrowseUnit ;-)
Romain
Avi