Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[PHPunit] suite variable should be used#26612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:3.4fromPrisisForks:3.4
Mar 21, 2018
Merged

[PHPunit] suite variable should be used#26612

fabpot merged 1 commit intosymfony:3.4fromPrisisForks:3.4
Mar 21, 2018

Conversation

@prisis
Copy link
Contributor

QA
Branch?3.4
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets
LicenseMIT

If you using phpunit V7 with the CoverageListener you getting a error withUndefined variable: test

lyrixx and gmponos reacted with thumbs up emoji
@fabpot
Copy link
Member

Thank you@prisis.

prisis reacted with thumbs up emoji

@fabpotfabpot merged commit8b8541e intosymfony:3.4Mar 21, 2018
fabpot added a commit that referenced this pull requestMar 21, 2018
This PR was merged into the 3.4 branch.Discussion----------[PHPunit] suite variable should be used| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets || License       | MITIf you using phpunit V7 with the CoverageListener you getting a error with `Undefined variable: test`Commits-------8b8541e [PHPunit] suite variable should be used
@prisisprisis deleted the 3.4 branchMarch 21, 2018 08:35
This was referencedApr 3, 2018
@greg0ire
Copy link
Contributor

Good catch, but wrong fix I'm afraid. Right now I'm getting this failure:

There was 1 failure:1) Symfony\Bridge\PhpUnit\Tests\CoverageListenerTest::testFailed asserting that 'PHPUnit 7.3.5 by Sebastian Bergmann and contributors.\n\n.....                                                               5 / 5 (100%)\n\nTime: 74 ms, Memory: 24.69MB\n\nOK (5 tests, 5 assertions)\n\n\nCode Coverage Report:   \n  2018-09-16 14:47:32   \n                        \n Summary:               \n  Classes: 100.00% (2/2)\n  Methods: 100.00% (3/3)\n  Lines:   100.00% (4/4)\n\n\PhpUnitCoverageTest::PhpUnitCoverageTest\BarCov\n  Methods: 100.00% ( 2/ 2)   Lines: 100.00% (  3/  3)\n\PhpUnitCoverageTest::PhpUnitCoverageTest\FooCov\n  Methods: 100.00% ( 1/ 1)   Lines: 100.00% (  1/  1)' does not contain "FooCov"./home/greg/dev/symfony/src/Symfony/Bridge/PhpUnit/Tests/CoverageListenerTest.php:36

A PR is on its way :)

greg0ire added a commit to greg0ire/symfony that referenced this pull requestSep 16, 2018
Calling the trait with a TestSuite argument will have no effect, it willexit quickly because of a test added in25e0117, that checks that $suite is a TestCaseinstance.Refssymfony#26612
greg0ire added a commit to greg0ire/symfony that referenced this pull requestSep 16, 2018
Calling the trait with a TestSuite argument will have no effect, it willexit quickly because of a test added in25e0117, that checks that $suite is a TestCaseinstance.Refssymfony#26612
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fabpotfabpotfabpot approved these changes

@lyrixxlyrixxlyrixx approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@prisis@fabpot@greg0ire@lyrixx@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp