-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Enhancement: Declare test code in subdirectories with separate configuration files #4
base: main
Are you sure you want to change the base?
Enhancement: Declare test code in subdirectories with separate configuration files #4
Conversation
b9fc574
to
23afcf0
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4 +/- ##
========================================
Coverage ? 100.00%
Complexity ? 8
========================================
Files ? 3
Lines ? 16
Branches ? 0
========================================
Hits ? 16
Misses ? 0
Partials ? 0 ☔ View full report in Codecov by Sentry. |
a4680d9
to
9256734
Compare
@@ -1,5 +1,6 @@ | |||
/.github/ export-ignore | |||
/.phive/ export-ignore | |||
/src/Test/ export-ignore |
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.
When you work on a package and declare test code in subdirectories of the production code with separate configuration files, adding exclusions for test code in .gitattributes
is even less work.
There is no need to add configuration files as they are in the excluded directory.
<exclude> | ||
<directory>.</directory> | ||
<directory>../Performance/</directory> | ||
<directory>../Util/</directory> | ||
</exclude> |
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.
When you declare test code in subdirectories of production code with separate configuration files, managing exclusions for collecting code coverage with phpunit/phpunit
in phpunit.xml
is a lot of work.
"exclude-from-classmap": [ | ||
"/src/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.
When you declare test code in subdirectories of production code with separate configuration files, managing exclusions for the composer
autoloader in composer.json
is less work.
0098fa7
to
4782eb6
Compare
590dafa
to
f3af23a
Compare
f3af23a
to
00227cf
Compare
This pull request
src/
with separate configuration files