-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Make QA tools available by default #81
Conversation
Signed-off-by: Aleksei Khudiakov <[email protected]>
Signed-off-by: Aleksei Khudiakov <[email protected]>
Signed-off-by: Aleksei Khudiakov <[email protected]>
a9a974a
to
b55dd0e
Compare
Signed-off-by: Aleksei Khudiakov <[email protected]>
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 think this is really good improvement. Just a couple of minor comments from me 👍
displayDetailsOnTestsThatTriggerErrors="true" | ||
displayDetailsOnTestsThatTriggerNotices="true" | ||
displayDetailsOnTestsThatTriggerWarnings="true" | ||
colors="true" |
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.
Do you think that failOnWarning
, failOnNotice
and friends would be too strict?
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 don't think this controls whether phpunit fails on warnings. This makes phpunit report tests that produced warnings or notices in test results.
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.
Sorry - I meant: Do you think that failOnWarning
and friends should be added to PHPUnit's config?
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.
They should.
Not the decision I am going to make here. We don't use them. Users can tighten configuration themselves.
Signed-off-by: Aleksei Khudiakov <[email protected]>
Description
Default installation results in tests, static analysis and coding standard tools are unusable. By making sure QA tools are immediately available and passing with
composer test
,composer cs-check
andcomposer static-analysis
we can promote their adoption and provide better starting point for our users.I included phpstorm and psalm stubs for container that I often find in my own projects. While it is not a strict relation between class-string id and actual returned instance it tends to be true often enough.