Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When there are a lot of issues to be fixed (like in the Diff module), the output of dmu-analyze borders on unreadable. It needs pretty formatting, stat. I need input from a UI/usability person on this.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Screen Shot 2014-09-17 at 9.05.49 PM.png | 63.08 KB | webchick |
Comments
Comment #1
webchickA couple of ideas that came up on the call:
1) Create an HTML report, rather than command-line.
2) "Pretty print" it using a utility like the one in PHPUnit.
Comment #2
tim.plunkettJust as a pointer, to see how PHPUnit does it:
PHP_CodeCoverage_Report_HTML is the main class, which references several Renderers, like PHP_CodeCoverage_Report_HTML_Renderer_File.
This is all kicked off by PHPUnit_TextUI_TestRunner.
Comment #3
phenaproximadmu-analyze will now output a pretty HTML file using Twig. Plugin annotations need to be changed to adapt (so far only InfoToYAML has been updated), but I'm calling this fixed anyway!
Comment #4
webchickStarting to look real slick! :D
One thing we definitely need still though is a pointer in the dmu-analyze command-line output to explain to people what happened. We can do that here or in another issue.
Comment #5
webchickFor posterity, screenshot of current output.
Comment #6
phenaproxima