and still get the output of accumulated errors? My environment is awful, slow, and not modifiable. (Just don't go there! At least I get to program in Ruby, which makes up for everything else.) So when I see some errors in a 300 example test file, it takes a long time (many minutes) for the file to finish out and give me some meaningful output to start debugging. Is there a way to send a signal to the rspec process and have it terminate and printout the accumulated errors up to that point? TIA, -Robert
on 2010-02-23 20:53
on 2010-02-23 20:54
On 23 Feb 2010, at 19:11, rlw wrote: > TIA, > -Robert Why don't you fiddle with the formatters to output the failures into another file, and then just tail that file for your meaningful output? cheers, Matt http://mattwynne.net +447974 430184
on 2010-02-23 22:45
This sounds relatively straightforward - I didn't know it was a possibility to dump the errors out as things were running. Anyone have sample code? TIA, -Robert
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.