Add "stop after ..." option

[thekid]

Reason

Practical for situations in which a large number of tests fail due to e.g. a refactoring. Running all tests tests takes too long and spits out hundreds of lines of stack traces, not aiding in solving the problem in a concentrated manner.

Current usage

$ unittest [options] test [test [test...]]

Options is one of:

• -v : Be verbose
• -q : Be quiet (no output)
• -cp: Add classpath elements
• -a {argument}: Define argument to pass to tests (may be used multiple times)
• -l {listener.class.Name} {output} [-o option value [-o ...]] where output is either "-" for console output or a file name. Options with "-o" are listener-dependant arguments.
• --color={mode} : Enable / disable color; mode can be one of
  • "on" - activate color mode
  • "off" - disable color mode
  • "auto" - try to determine whether colors are supported and enable accordingly.
• -w {dir}: Run indefinitely, watch given directory for changes

  New option

• -s {when}: Stop after the following occurs, where when is one of
  • "fail" - The first failing test
  • "skip" - The first skipped test
  • "ignore" - The first ignored test

    See also

• Stop JUnit before you get into trouble.