This is now an archive web site. Some is still relevant as at February 2026 but some is purely of historic interest.
Lisa and I (Graham) are now fully retired from IT training.We have made many friends over 30 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Apache, Linux and Solaris/SunOS too. Our training notes are out of date, but with upward compatability some examples remain operational and relevant. You are welcome to make use of them "as seen", at your own risk. We now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We remain active, enjoying the times that we are retired but still healthy enough in mind and body to do things!
I am also active in many other area and still look after a lot of web sites - you can find an index ((here)) |
|
Testing code coverage (have I tested everything?) in PHP (written 2012-12-21)
When you write a series of tests for your code and they all pass, have you tested everything? Not Necessarily - you only know that you have passed all the tests that you set, and not that the test set could be considered to be complete.
PHPUnit - the unit test suite for PHP - includes a coverage option which will let you check whether each class and method of the code that you're testing has been run as a part of the tests, and will tell you how many times each statement has been executed during testing. Simply run the phpunit command with the appropriate option:
phpunit --coverage-html /var/www/html/cover five.php
As the results are extensive, they don't come as a single file but rather as a complete web folder, and in my command I've redirected that to a directory that's within my web document root so that I can browse to it:
And I can also explore the source code and the number of times each conditional group of statements / loop has been run:
For details of writing the tests for PHPunit, see previous article [here]. (written 2012-12-21, updated 2012-12-22)
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articles H311 - Testing your PHP [3426] Automed web site testing scripted in Ruby using watir-webdriver - (2011-09-09) [3623] Some TestWise examples - helping use Ruby code to check your web site operation - (2012-02-24) [3958] Testing classes for your PHP website with PHPUnit - (2012-12-20) [4652] Testing new algorithms in PHP - (2016-02-20)
Some other Articles
National TV - Melksham - 9th January 2013, Pre-alert.Melksham welcomes visitors - new blue plaque trail and moreWell House Staff PartyPicture - between Lacock and MelkshamTesting code coverage (have I tested everything?) in PHPThe week before ChristmasZend / layout of MVC and other files in an example application (PHP)Building up from a small PHP setup to an enterprise one Lesson 1 in programing - write clean, reuseable and maintainable tidy code
|
4759 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96 at 50 posts per page
This is a page archived from The Horse's Mouth at
http://www.wellho.net/horse/ -
the diary and writings of Graham Ellis.
Every attempt was made to provide current information at the time the
page was written, but things do move forward in our business - new software
releases, price changes, new techniques. So much so, and it's so long ago
that we are retired
Link to Ezine home page (for reading).
|
|