Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Attached is a patch to allow code coverage on drupal 7 unstable. I have only checked the HTML report.
@cwgordon,
this night I'm running a full coverage report on Core. Do you mind me release this somewhere or are you going to do this again on the initial coverage site?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | unstable_9.1.patch | 11.48 KB | berdir |
| #1 | coverage.patch | 1.94 KB | berdir |
| unstable_9.patch | 12.96 KB | R.Muilwijk |
Comments
Comment #1
berdirUpdated the patch...
- Fixed some DBTNG stuff
- Improved parsing of the coverage logfile. According to my tests, just the parsing (moving information into $data) is now 2-3x faster and uses *a lot* less memory:
Testing with an 80MB file, Before:
Total time: 234.750s
Memory usage: 170,135,096 bytes
After:
Total time: 89.968s
Memory usage: 10,627,856 bytes
Note that the patch does not patch the coverage.patch file because it's not part of repository anymore.
Comment #2
boombatower commented#738980: Refactor/Rewrite should everything except settings which I will be working on soon.
Comment #3
berdirSep 09? I totally forgot about this issue or I'd mentioned it to you when we talked about code_coverage.module :)
Comment #4
boombatower commentedI just took over maintaining this module, so fixing it up. :) No activity for over a year.