stv0g/Criterion
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
Criterion/test/cram/exit.t

36 lines
2.6 KiB
Perl
Raw Permalink Normal View History

Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
Testing tests that call exit()
$ exit.c.bin --verbose
release: Prepare a release candidate for 2.3.0
2016-09-19 00:21:17 +02:00
[\x1b[0;34m----\x1b[0m] Criterion v2.3.0-rc1 (esc)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34m====\x1b[0m] Running \x1b[0;34m3\x1b[0m tests from \x1b[0;33mexit\x1b[0m: (esc)
[\x1b[0;34mRUN \x1b[0m] exit::expected_exit (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;32mPASS\\x1b\[0m\] exit::expected_exit: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34mRUN \x1b[0m] exit::normal (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;32mPASS\\x1b\[0m\] exit::normal: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34mRUN \x1b[0m] exit::unexpected_exit (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;31mFAIL\\x1b\[0m\] exit::unexpected_exit: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34m====\x1b[0m] Running \x1b[0;34m2\x1b[0m tests from \x1b[0;33mexit_with_fixtures\x1b[0m: (esc)
[\x1b[0;34mRUN \x1b[0m] exit_with_fixtures::fini_exits (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;32mPASS\\x1b\[0m\] exit_with_fixtures::fini_exits: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34m----\x1b[0m] \x1b[0;1mWarning! The test `exit_with_fixtures::fini_exits` exited during its setup or teardown.\x1b[0m (esc)
[\x1b[0;34mRUN \x1b[0m] exit_with_fixtures::init_exits (esc)
[\x1b[0;34m----\x1b[0m] \x1b[0;1mWarning! The test `exit_with_fixtures::init_exits` exited during its setup or teardown.\x1b[0m (esc)
core: `.exit_code = 0` now enforces the test exit status to be 0. Before this change, an exit_code of 0 would allow a test to pass for any exit status, because checking for 0 meant that the value was optional and people did not care. However, the semantics of exit() tells that 0 shall be synonymous of success, and allowing a nonzero status to pass the test is unexpected. This fixes issue #137.
2016-07-28 18:11:45 +02:00
[\x1b[0;34m====\x1b[0m] \x1b[0;1mSynthesis: Tested: \x1b[0;34m5\x1b[0;1m | Passing: \x1b[0;32m3\x1b[0;1m | Failing: \x1b[0;31m2\x1b[0;1m | Crashing: \x1b[0;31m1\x1b[0;1m \x1b[0m (esc)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
$ exit.cc.bin --verbose
release: Prepare a release candidate for 2.3.0
2016-09-19 00:21:17 +02:00
[\x1b[0;34m----\x1b[0m] Criterion v2.3.0-rc1 (esc)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34m====\x1b[0m] Running \x1b[0;34m3\x1b[0m tests from \x1b[0;33mexit\x1b[0m: (esc)
[\x1b[0;34mRUN \x1b[0m] exit::expected_exit (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;32mPASS\\x1b\[0m\] exit::expected_exit: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34mRUN \x1b[0m] exit::normal (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;32mPASS\\x1b\[0m\] exit::normal: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34mRUN \x1b[0m] exit::unexpected_exit (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;31mFAIL\\x1b\[0m\] exit::unexpected_exit: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34m====\x1b[0m] Running \x1b[0;34m2\x1b[0m tests from \x1b[0;33mexit_with_fixtures\x1b[0m: (esc)
[\x1b[0;34mRUN \x1b[0m] exit_with_fixtures::fini_exits (esc)
cram: Fixed tests to account for time
2016-09-04 12:19:56 +02:00
\[\\x1b\[0;32mPASS\\x1b\[0m\] exit_with_fixtures::fini_exits: \(\d\.\d\ds\) \(esc\) (re)
Added the rest of the cram tests and removed old system test suite
2016-01-16 13:24:35 +01:00
[\x1b[0;34m----\x1b[0m] \x1b[0;1mWarning! The test `exit_with_fixtures::fini_exits` exited during its setup or teardown.\x1b[0m (esc)
[\x1b[0;34mRUN \x1b[0m] exit_with_fixtures::init_exits (esc)
[\x1b[0;34m----\x1b[0m] \x1b[0;1mWarning! The test `exit_with_fixtures::init_exits` exited during its setup or teardown.\x1b[0m (esc)
core: `.exit_code = 0` now enforces the test exit status to be 0. Before this change, an exit_code of 0 would allow a test to pass for any exit status, because checking for 0 meant that the value was optional and people did not care. However, the semantics of exit() tells that 0 shall be synonymous of success, and allowing a nonzero status to pass the test is unexpected. This fixes issue #137.
2016-07-28 18:11:45 +02:00
[\x1b[0;34m====\x1b[0m] \x1b[0;1mSynthesis: Tested: \x1b[0;34m5\x1b[0;1m | Passing: \x1b[0;32m3\x1b[0;1m | Failing: \x1b[0;31m2\x1b[0;1m | Crashing: \x1b[0;31m1\x1b[0;1m \x1b[0m (esc)
Reference in a new issue Copy permalink