Note re: Unit Tests

[Ian]

Just a note regarding a recent change to the unit testing suite for those who are trying to run them.  Output buffering was recently enabled at the start of the script presumably to facilitate session tests.  As a result, PHPUnit will not display any output until all the tests are complete.  If you run phpunit and it appears to just hang, that is normal.  Just give the tests time to complete and you will see all the results at the end.

Ian

[Stefan Neculai]

Hey,

Is it there any possibility to make the output still show while running the tests? I find the output during the test really useful.

--

Thanks,

Stefan

[Rouven Weßling]

Unfortunately our (few) tests for JSession require this for now. If you find a way to rewrite them that this isn't necessary anymore that be very welcome.

Rouven

[Stefan Neculai]

Hi,

I was rather thinking at an option to set in bootstrap so everyone can enable and disable it easily. Developers can let it enabled when they run session tests and disable otherwise.

--

Stefan

[Ian]

You still do get the results at the end, you just have to wait until everything is complete.

It isn't too bad so long as you use filter to only run the tests you actually want to test.

Something else that might be reasonable, so long as all the JSession tests are in one class (which I didn't look to check) would be to end output buffering in the tearDownAfterClass so that you would get the normal progress report as soon as the session tests were done.

Anyway, just thoughts.

Ian