Commit e92f2a82 authored by Mathieu Giraud's avatar Mathieu Giraud

demo/retry.should: --retry, --retry-warned

parent 0dfd6924
# should.py --retry relaunches the previous failed or warned tests,
# with the same options that at the first call.
# should.py --retry relaunches the previous failed tests.
# should.py --retry-warned relaunches the previous failed or warned tests.
# These relaunches are with the same options that at the first call.
./should -v demo/hello.should demo/cal.should
./should --retry
!EXIT_CODE: 1
./should -v demo/hello.should demo/cal.should demo/tests/fail.should
./should --retry-warned
$ 'cal.should' was labeled as 'TODO' at both calls
rl: files with.*TODO.*demo/cal.should.*Retrying
rl: Retrying .*files with.*TODO.*demo/cal.should
$ At the second call, 'cal.should' is tested, but not 'hello.should'
$ At the second call (--retry-warned), 'fail.should' and 'cal.should' are tested, but not 'hello.should'
r0l: Retrying .* demo/hello.should
r1l: Retrying .* demo/cal.should
r1l: Retrying .* demo/tests/fail.should
$ The option '-v' was used at both calls
rl: 7 months have 31 days.*Retrying
rl: Retrying.*7 months have 31 days
./should --retry
$ Now only 'fail.should' is tested
r0l: Retrying .* demo/hello.should
r0l: Retrying .* demo/cal.should
r1l: Retrying .* demo/tests/fail.should
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment