requirements / what should be implemented

[bscheshirwork]

code

• tests/bootstrap.php - include require, exclude alias
• tests/compatibility.php - fix all of parent issues like this 14973, 126
• tests/TestCase.php - general base class

docs

• about this repo / README.md
• how to set up travis configuration
• how to set up local tests

I have a guide-ru example for docs: here
codeception; see PhpStorm_Codeception_ReportPrinter_Redefine chapter for avoid output after header send

[bscheshirwork]

I think we need docker-compose.yml with php included PHPUnit example too

[samdark]

Not sure about docker (since it it can't be used without the phpunit itself and separately from tests) but agree about the rest.

[sergeymakinen]

https://github.com/sergeymakinen/tests could be useful although there are many "right" ways to accomplish this.

[rob006]

I don't think that we need bootstrap.php (it is project-specific) or compatibility.php (it is not required anymore). All we need is TestCase and custom assertions. Compatibility hacks should go directly to TestCase - this should be really easy if we bound extension version to phpunit version:

• 2.0.x requires phpunit 4, so TestCase contains only methods unavailable in phpunit 4 but available in phpunit 6.
• 2.1.x requires phpunit 5 and contains only methods unavailable in phpunit 5 but available in phpunit 6.
• 2.2.x requires phpunit 6 and contains only custom assertions.