? ? Success

User tests: Successful: Unsuccessful:

avatar roland-d
roland-d
3 Oct 2015

When running the unit test, it would generate this error:

Test code or tested code did not (only) close its own output buffers

This error is generated because the triggerManifestScript() method would run into an error and then throws a RuntimeException without closing the output buffers which were opened. This change cleans and closes the output buffer as the output is not used anyway.

Test instructions
Only way I can see this tested is that you run the unit test and see the error, after applying the patch the error is gone.

Normal installation of an extension which fails should also still behave as usual.

avatar roland-d roland-d - open - 3 Oct 2015
avatar roland-d roland-d - change - 3 Oct 2015
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 3 Oct 2015
Labels Added: ?
avatar zero-24 zero-24 - change - 5 Oct 2015
Labels Added: ?
avatar zero-24 zero-24 - change - 5 Oct 2015
Category Libraries Unit Tests
avatar zero-24 zero-24 - change - 5 Oct 2015
Easy No Yes
avatar wilsonge
wilsonge - comment - 8 Oct 2015

This seems right - but what unit test do you mean? I don't see anything in the travis output logs?

avatar roland-d
roland-d - comment - 22 Oct 2015

Check the screenshot, this is where I get these errors:
image

avatar wilsonge wilsonge - change - 6 Mar 2016
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2016-03-06 23:06:59
Closed_By wilsonge
avatar wilsonge wilsonge - reference | b51fefd - 6 Mar 16
avatar wilsonge wilsonge - merge - 6 Mar 2016
avatar wilsonge wilsonge - close - 6 Mar 2016
avatar wilsonge
wilsonge - comment - 6 Mar 2016

These were showing as Risky Tests on travis - hence why they were hidden. Merged

avatar wilsonge wilsonge - change - 6 Mar 2016
Milestone Added:

Add a Comment

Login with GitHub to post a comment