-
Notifications
You must be signed in to change notification settings - Fork 50
Moved TEST_COMMAND to global section #203
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
766687e
d78cddc
3389c8a
cf5a957
81efd33
8ad73b5
8bc901f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,10 +29,11 @@ | |
"php-http/message": "^1.4", | ||
"php-http/discovery": "^1.0", | ||
"twig/twig": "^1.18 || ^2.0", | ||
"symfony/asset": "^2.8 || ^3.0" | ||
"symfony/asset": "^2.8 || ^3.0", | ||
"symfony/symfony": "2.8.27" | ||
}, | ||
"require-dev": { | ||
"phpunit/phpunit": "^4.5 || ^5.4", | ||
"phpunit/phpunit": "^4.8.35 || ^5.7 || ^6.1", | ||
"phpunit/php-token-stream": "^1.1.8", | ||
"php-http/curl-client": "^1.0", | ||
"php-http/socket-client": "^1.0", | ||
|
@@ -49,7 +50,7 @@ | |
"symfony/browser-kit": "^2.8 || ^3.0", | ||
"symfony/dom-crawler": "^2.8 || ^3.0", | ||
"polishsymfonycommunity/symfony-mocker-container": "^1.0", | ||
"matthiasnoback/symfony-dependency-injection-test": "^1.0", | ||
"matthiasnoback/symfony-dependency-injection-test": "^1.0 || ^2.0", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we need both versions to support the range of php versions we support? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, we can't install PHPUnit 6.0 because of a conflict on |
||
"nyholm/nsa": "^1.1" | ||
}, | ||
"conflict": { | ||
|
@@ -60,6 +61,11 @@ | |
"Http\\HttplugBundle\\": "" | ||
} | ||
}, | ||
"autoload-dev": { | ||
"classmap": [ | ||
"Tests/Resources/app/AppKernel.php" | ||
] | ||
}, | ||
"scripts": { | ||
"test": "vendor/bin/phpunit", | ||
"test-ci": "vendor/bin/phpunit --coverage-text --coverage-clover=build/coverage.xml" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i discussed once with sebastian bergman and he is saying he agrees that the annotation is less clean than calling setExpectedException. the reason is that if the exception is thrown too early, the test would wrongly be green. this is particularly true when we expect such a generic exception
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, it's better to have a if/else at the right position in the test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why if/else? afaik the $this->setExpectedException call is the best practice way. this makes sure the exception is only considered correct when thrown after that line in the code, and you have namespace resolution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
setExpectedException
was removed in 6.0 and replaced byexpectException
. That's why I moved to annotation.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, We need the annotation for BC purpose...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can keep this as-is and switch to
expectException
in next-major.