Test cases could be run as child processes

jorsanpe commented 4 years ago

This is a suggestion for a possible enhancement. Running each test case as a child process could have a number of advantages:

Capturing stdout, stderr. This would improve the console output, as the output generated by the SUT could be captured and displayed orderly.
Capturing terminating signals. If a SUT raises for example a SIGSEGV, then the entire program is terminated and no more tests are run. By forking the process, the child process would die but the parent process (the test runner), could display information about the crash.

This feature has portability concerns. If Cest is intended to be as portable as possible, then some mechanism should be in place to allow platform independent process spawning.

cegonse commented 4 years ago

Potentially related to #41

cegonse commented 1 week ago

This will be solved as soon as version v2 comes out. Now you can use cest-runner to run all test suites, which are run inside a separate sub-process. Then, if a single test raises a signal and the execution of other tests is recoverable through longjmp it will be captured by the runner:

And if the signal is raised at the top level and is not recoverable, the runner will mark the whole suite as failed:

cegonse / cest

Test cases could be run as child processes #38