Created by: ybelenko
I've found markTestIncomplete method in PHPUnit. It perfectly fits our autogeneration flow.
Ref: PHPUnit 7.0 Manual - 7. Incomplete and Skipped Tests
Result of tests:
$ composer test
> phpunit
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.
IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII.II.II.IIIIIIIIIIII.II.I 63 / 520 ( 12%)
I.II.II.III.IIII.II.II.IIII.II.IIIII.IIIIIII.II.IIII.III.II.II. 126 / 520 ( 24%)
II.IIII.III.I.IIIIII.III.II.IIIIIIIIIIIIIII.III.IIIII.IIII.III. 189 / 520 ( 36%)
II.II.IIIII.II.IIIIIII.IIII.I.IIIIIII.III.II.III.IIIIII.IIIIIII 252 / 520 ( 48%)
.IIIIIIIII.IIIIIIIIIIIIIIIIIIIIIIIIIIIIII...................... 315 / 520 ( 60%)
............................................................... 378 / 520 ( 72%)
............................................................... 441 / 520 ( 84%)
............................................................... 504 / 520 ( 96%)
................ 520 / 520 (100%)
Time: 2.88 seconds, Memory: 18.00 MB
OK, but incomplete, skipped, or risky tests!
Tests: 520, Assertions: 8004, Incomplete: 246.PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master,4.3.x,5.0.x. Default:master. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.
cc @jebentier @dkarlovi @mandrean @jfastnacht @ackintosh @renepardon