Can't disable exception trace

[PabloReyes]

When running a failing unit test, the exception trace is shown after each test is executed:

4) DBConstraintsTest::testABC
Failed asserting that '2' matches expected 0.

codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/Constraint/IsEqual.php:170
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/Assert.php:2134
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/Assert.php:475
/.../tests/unit/DBConstraintsTest.php:97
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:983
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:838
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/TestResult.php:648
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/TestCase.php:783
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:775
codecept.phar/vendor/phpunit/phpunit/PHPUnit/Framework/TestSuite.php:745

After some researching, I found that it may be caused by xdebug being activated (although PHPUnit deactivates by default), so I added this to my _bootstrap.php:

xdebug_disable();
ini_set('xdebug.show_exception_trace', 0);

Yes, both, just in case. But it still appeared, so I limited the TRACE LEVEL to see if it affected in any way:

define('YII_TRACE_LEVEL',0);

It didn't change anything. I edited my CLI php.ini file to set xdebug.show_exception_trace and restarted apache. Nothing. I tried running the test with --debug and without it, but still no changes.

I have searched the documentation but can't find anything. All the test are being run from the terminal, no IDE. I also use the Yii1 module.

Is there any way to disable that output, or is it just a bug?

Thanks

[DavertMik]

Not bug but a feature :) Not really sure why would you need to disable the stacktrace.
If you don't need verbose output just run with --silent option.

Codeception stack trace has nothing to do with xdebug or yii stack trace.
It is used to show you the place where error occur. Which is quite usefulf for fixing failed test

[PabloReyes]

Sorry DavertMik, I don't really agree with that. That exception trace doesn't help finding why my test failed, it just show the trace of the assertEquals code, linking to code I cannot even debug since it's on the phpunit inside codecept.phar.

And of course, all traces are always the same (if using assertEquals), so I end up with a terminal full of repeated exceptions that doesnt have anything to do with my code.

Thanks!

[DavertMik]

I did some work to clean up the traces, so you should only see lines of your code, and no lines of Codeception framework. So for your example you should see only:

/.../tests/unit/DBConstraintsTest.php:97

Which is just enough to find the place where the test fails.
Already implemented in master branch, and will be in 1.8

[PabloReyes]

Thank you so much, that's exactly what I needed :)