-
Notifications
You must be signed in to change notification settings - Fork 10
Code coverage of tests should be 100% #96
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
sounds reasonable. But I'm not sure if entirely convinced about this as I remember some PHPUnit-related issues where i.e. a closing bracket was untested code, so I couldn't reach 100% coverage in some side-projects back then. But please correct me if I'm wrong, I didn't do too much PHP in the last year 😄 |
I did have a look into the coverage HTML report and IIRC there is indeed one line (or condition?) that's currently not tested. |
xalopp
added a commit
to xalopp/mo4-coding-standard
that referenced
this issue
Oct 19, 2018
xalopp
added a commit
to xalopp/mo4-coding-standard
that referenced
this issue
Oct 19, 2018
mmoll
pushed a commit
to mmoll/mo4-coding-standard
that referenced
this issue
Oct 23, 2018
(cherry picked from commit d1d9864)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
To increase confidence, we should look to have a code coverage of 💯
The text was updated successfully, but these errors were encountered: