Is this expected behaviour?

[lightiverson]

It seems when passing a user defined exit code to a test, Criterion ignores any other assertions. Take the attached screenshot for example, shouldn't this test fail because of the false assertion?

[Snaipe]

Your cr_assert_stderr_eq_str never runs, because error() exits the process by calling exit(0). This behavior is quite normal.

[lightiverson]

Ah, that makes sense. Thanks!

[lightiverson]

Is there any way to check for cr_assert_stderr_eq_str as well as a custom .exit_code coming from the same function?

[Snaipe]

Well, if cr_assert_eq_str runs before your test exits, then yes, it would work. .exit_code is simply a way to check that the entire test must exit with a specific exit status, but you can run any number of assertions between the start and the call to exit.