timing

HISTORY

@@ -151,6 +151,20 @@ If you don't explicitly specify the Urchin root with a .urchin file, we
 consider the test suite root directory to be the parent of the file that
 you ran Urchin on.
 
+### Verbose output
+
+### Timing
+Urchin now reports the time, in seconds, that each test took and also the
+total time that it took to run the whole test suite.
+
+Urchin also allows you to set timeouts, in seconds, with the --timeout flag.
+If you set a timeout flag and a test file takes longer to run, that run will
+be killed, and the test will thus fail. The standard error message from the
+timeout program will show up in the test output.
+
+Both of these timers use the real time (not the CPU time for example),
+so the times are not very precise and may be much larger than you expect.
+
 Version 0.0.6
 ---------------------
 

TODO

@@ -79,15 +79,3 @@ in the case of Urchin.
 This is as far as I have gotten with contemplating license changes. For now
 we're sticking with the original MIT-style license, but it's easy to change
 licenses later.
-
-Running automated tasks
--------------------------
-Urchin might be appropriate for if you have lots of tasks that you want to run
-periodically; add an urchin call to your crontab, and call all of your other
-tasks with urchin. Here are some features that might make urchin better for
-this sort of thing.
-                                                      
-* Time how long each test/job takes
-* Optionally kill tests/jobs after a specific timeout threshold
-* Send output of different tests/jobs to different files for each file
-  descriptor (STDOUT, STDERR)