You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
assertResponseStatusCode() and assertNotResponseStatusCode throw an exception for console controller tests if the argument is not 0 or 1.
I don't see a reason for this limitation. Exit codes can have a broad range of values, and it's common practice to report specific error conditions. A ZF console application works fine with arbitrary exit codes. There are platform-specific limitations, but these are outside the scope of the test routine.
assertResponseStatusCode() and assertNotResponseStatusCode throw an exception for console controller tests if the argument is not 0 or 1.
I don't see a reason for this limitation. Exit codes can have a broad range of values, and it's common practice to report specific error conditions. A ZF console application works fine with arbitrary exit codes. There are platform-specific limitations, but these are outside the scope of the test routine.
I can work around the limitation:
but unless I'm missing something, assertResponseStatusCode() should not perform any range checks at all.
The text was updated successfully, but these errors were encountered: