In a (in portuguese) I explained how to identify tests that are taking too long to execute. In this post, I’ll show you how to increase the performance of code coverage report generation using . previous post PHPUnit In the phpunit.xml file it’s possible to add configurations to generate reports related to the tests that are being executed. For example: A directory named “tests/_reports” will be created and will contain a series of useful information. In the coverage-html directory we can see code test coverage details that facilitate the analysis. The file clover.xml is just another version of the same information to be processed by services such as Jenkins, CodeCov, Coveralls, Codacy, and others, to automate alerts and scripts. In addition to changing the phpunit.xml file, to generate this information we also need to install the extension XDebug. However, by installing it we get a substantial decrease in performance. Check the test execution results without generating the reports: Now, when we add XDebug and execute it again we get: The execution time jumped from 1.08 to 22.26 minutes! After some research online I found and decided to give a try. this post phpdbg Since I’m using MacOS X for this test, I executed the commands below to install all the necessary dependencies. The main difference is the parameter –with-phpdbg used in php7’s installation. By following from Sebastian Bergmann, PHPUnit’s creator, I found the syntax to run the test again: this post phpdbg -qrr ./vendor/bin/phpunit 1.59 minutes is much better than the 22.26 minutes it takes with XDebug. Excited with the results I twitted the following, even before writing this post: If you take a look at the comment, Derick Rethans is no one other than the creator of XDebug! Taking his comment into account, I compared the results generated by XDebug and phpdbg. Below is the comparison of coverage-html generated by XDebug (left) and phpdbg (right). I then used CodeCov to process the clover.xml file and the result was also a little bit different: phpdbg XDebug According to the report generated by phpdbg Planrockr has 66.05% of code coverage. XDebug’s report shows the code coverage at 65.92% Some conclusions I draw from this small test: XDebug is an incredible tool and does a lot more than generate code coverage, so I’m not saying here that you should stop using it. I’m just comparing one of its many functionalities. I compared the default results, without making any adjustments to the configurations of XDebug or phpdbg, thus other scenarios can have different results. Although there is a slight difference between the two results, in my case, it does compensate to use phpdbg due to its better performance. I’ll continue to use phpdbg for a while and if I happen to see any different results I’ll update this post or will write another one about the experience. If by any means you think my conclusions are wrong, please don’t hesitate to contact me to let me know. is how hackers start their afternoons. We’re a part of the family. We are now and happy to opportunities. Hacker Noon @AMI accepting submissions discuss advertising &sponsorship To learn more, , , or simply, read our about page like/message us on Facebook tweet/DM @HackerNoon. If you enjoyed this story, we recommend reading our and . Until next time, don’t take the realities of the world for granted! latest tech stories trending tech stories

Facebook

Continuous integration in projects using monorepo

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Generating Code Coverage with PHPUnit and phpdbg

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Continuous integration in projects using monorepo

10 Use Cases for Using Laravel to Build Web App Development Projects

2.6 Million Domains and ~45,000 Exposed Phpinfo() Later… the Story of Unprotected Phpinfo()

2016 In Review: The Year of Exploits

20 principles for Craft CMS

Continuous integration in projects using monorepo

10 Use Cases for Using Laravel to Build Web App Development Projects

2.6 Million Domains and ~45,000 Exposed Phpinfo() Later… the Story of Unprotected Phpinfo()

2016 In Review: The Year of Exploits

20 principles for Craft CMS

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps