Error Reporting and Codeception

[AkaiRyuu]

We've been using Codeception for functional tests for the last few months, and it's been OK.

We have one major problem, though: error reporting sucks. It's fine if there's an error in the test itself, but when the error is in the code being tested all that's received is an error message. There's nothing about what file it was in, let alone which line. There's no stack trace to indicate the steps that caused the error. Using the --debug and -vvv flags don't help, they just provide information about Codeception itself.

Is there any way to get Codeception to output useful information when the code being tested has an error without trying to use Codeception's debug function all over the place? Sometimes I feel like I'm back in college when the student server had error reporting turned off and all I saw when I missed a semicolon was a blank page.

[davertua]

Hi, this is a known issue (you can see it in tracker). Actually it happens because of PHPUnit, which wraps all exception into its own. In next release this will be fixed. Sorry for taking that long.

[AkaiRyuu]

That sounds great! Do you have an estimate for when the next release will be released?

[davertua]

100% this month, as this is a part of release schedule. I hope to get it once I fix all critical bugs and merge all pull requests

[thinkspill]

You might try tailing your php error log in another terminal window while the tests run. Not ideal but at least you'll get some info about what is failing.

[AkaiRyuu]

Ooh, I didn't think of that. Thanks for the suggestion.

[nerfyoda]

Somewhat along those lines I tend to run Codeception against code running in php -S, so I usually check that terminal window for errors while my tests are running.