WIP Improvements to FeatureTestCaseTest

[jim-parry]

• added 'patch' to allowed HTTP verbs in RouteCollection
• added resetRoutes() in RouteCollection, to support FeatureTestCase
• added output capturing to FeatureTestCase::call
• added more methods to tests/_support/Controllers/Popcorn, to generate all the different kinds of responses
• added note to testing/features in user guide

Related to #1767, #1692 & possibly #1697

[lonnieezell]

@jim-parry I got it working for me in this branch. Does that work for you also?

[jim-parry]

testing

[jim-parry]

That does fix things :) I have incorporated the changes into my original PR & pushed. Now I can finish the tests, thanks!

[jim-parry]

Hmmm - the tests run locally fine as "./phpunit tests/system/Test/", but not as "./phpunit".
I don't see how that affects things, but will revisit in the morning :-/

[jim-parry]

travis-ci is breaking in SQLite3 stuff - not related to this PR as far as I can tell.
@lonnieezell what do you think - is there something else to fix, or is this good to merge?

[lonnieezell]

What were you running into here? Lastwrite should be null before it's used so that an initial call to 'write' will add an empty line.

[jim-parry]

The problem is that the previous unit tests were not looking for that empty line, and hence failed on mmy system. Basically, the previous PR broke that unit test on my system.

[lonnieezell]

These two might have been caused by these changes:

1. CodeIgniter\CodeIgniterTest::testRunClosureRoute
   Test code or tested code did not (only) close its own output buffers
2. CodeIgniter\CodeIgniterTest::testRun404OverrideByClosure
   Test code or tested code did not (only) close its own output buffers

No clue why the sqlite is failing now. Nothing in here should have touched that.

[jim-parry]

I have been getting some strange unit testing results with CodeIgniterTest and MigrationRunnerTest for some weeks now. I think it might be time to reclone & reconstruct my local repo :-/
I'm going to leave this PR unmerged for now, and deal with it properly when time permits. I'll tag it for the next release instead.