This is an old revision of the document!
Add decision and path coverage to Xdebug's code coverage instrumentation
The original application is http://socghop.appspot.com/student_project/show/google/gsoc2009/php/t124023312659
Details
- Student: Allister Beharry
- Mentor: Derick Rethans
- Timezone: UTC-4
- Mailing list: xdebug-dev@lists.xdebug.org
Abstract
Extend the code coverage instrumentation in Xdebug from statement coverage to include decision and path coverage. Xdebug will be able to report for a given block of code the number of unique branches, how many branches were executed during execution of the block, how many linearly independent paths exist through the code block, and which of these code paths were executed. A data structure representing which paths and branches were taken will be available to code coverage tools .
Initial Timeline
May 23rd - June 13th: Study closely PHP runtime, opcodes and extending PHP
June 13th - June 27th: Implement branch coverage statistics (counting branches executed / total branches)
June 27th - July 18th: Implement path coverage statistics (counting paths executed / total paths)
July 18th - August 1st Implement branch coverage data structure
August 1st - 24th Implement path coverage data structure
This will be refined as I go deeper into the project
Resources
http://blog.libssh2.org/index.php?/archives/92-Understanding-Opcodes.html - brief tutorial on opcodes http://www.zapt.info/opcodes.html list of opcodes with annotation http://www.phpcompiler.org/ a PHP compiler - profides a framework for manipulating ASTs