Codeception: "Command Did Not Finish Properly" with no additional information

Created on 29 Mar 2018  路  2Comments  路  Source: Codeception/Codeception

Most helpful comment

Duplicate of #4880

"Command Did Not Finish Properly" is an additional information itself - it means that application code called exit or die function.

Before introduction of "Command Did Not Finish Properly" test execution simply ended successfully ( or unsuccessfully, depending on exit code) with no output.

Current implementation does not intercept die and exit calls, it only checks if test suite was executed to completion, so it is impossible to tell where the die was called.

However if die/exit had a message parameter, that message is displayed below stack trace.

All 2 comments

Duplicate of #4880

"Command Did Not Finish Properly" is an additional information itself - it means that application code called exit or die function.

Before introduction of "Command Did Not Finish Properly" test execution simply ended successfully ( or unsuccessfully, depending on exit code) with no output.

Current implementation does not intercept die and exit calls, it only checks if test suite was executed to completion, so it is impossible to tell where the die was called.

However if die/exit had a message parameter, that message is displayed below stack trace.

@Naktibalda ty man man for the reply, I'm going to find this die/exit tommorow!

Was this page helpful?
0 / 5 - 0 ratings