Replies: 1 comment 4 replies
-
|
My opinions about code coverage: It is useful only for mutation testing, in order to characterize the code without proof of its behavior. So for me codecov is useless. |
Beta Was this translation helpful? Give feedback.
-
|
If not for the sake of chasing a 100% metric, but it gives a realistic picture of the code, whether there is still deprecation warning lurking in a file. If a file is not tested at all, it may be worth looking at. We don't really have a clear picture of that right now. |
Beta Was this translation helpful? Give feedback.
-
|
@connorhu Symfony1 is already set to PHP v7.4 as the lowest version now (See #325) |
Beta Was this translation helpful? Give feedback.
-
|
Current problem: We got a PR that changes a line in a file. In order to check that the change doesn't cause a BC break, I need to search out the tests for that section and look through what the tests test, one by one. Using code coverate report, I just check if that is tested and I know right away that I don't need to ask the PR owner for a test, just green status is enough. |
Beta Was this translation helpful? Give feedback.
-
|
@connorhu for that kind of use case you describe. Code coverage does not tell you if new code doesn't cause a BC break. Mutation testing is more useful to chase BC break. Code coverage is one step toward mutation testing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Do we want codecov integration where it is possible? For now, swiftmailer uses phpunit, but doctrine1 and symfony1 can be adapted in the foreseeable future. For symfony1 I would need php7.4 minimum to start integrating phpunit.
Beta Was this translation helpful? Give feedback.
All reactions