Jip
@soveran I think taking a copy at the moment of subclassing is cleanest. It would avoid situations where a cuba app tries to use a setting that isn't _guaranteed_ to...
+1 I think cutest should keep the default behaviour of failing fast. It's very useful while developing. Running all tests regardless of there being failures would be very useful for...
`-a` for all seems sensible. I think the usage string (in the executable) should be clearer, though. `[-a]` is not very clear on what it means.
Won't `$LOAD_PATH` often include the files that your code under test is stored in? If that's the case, you'll often end up with an empty stack trace.
That's true (though I know of at least one project where I'd end up with empty backtraces :blush:). Perhaps this is a good use case for Ruby's `awk` inheritance: `BEGIN...
Yes. Consider the / my typical Rakefile: ``` ruby $LOAD_PATH.unshift File.expand_path("./lib") require "cutest" # or require "test_helper" require "my_library" task(:foo) { MyLibrary.do_something! } task(:bar) { MyLibrary.do_something_else! } task(:test) { Cutest.run(FileList["test/*_test.rb"])...
My use case is similar. I depend on the return value in [a library](https://github.com/britishtea/stig) that makes it convenient to run multiple tests with random input to test if some property...
Im sorry, I'm not sure what you mean.
@maddox, I think I finally managed to do it right :s
I think https://github.com/httprb/http/issues/420 is related.