[#101] - Automated testing
- Closed
- 3 Nov 2013
- Medium
- Build: master
- # 101
The elephant in the room - automated testing
We've very largely ignored testing the code and probably should stop doing so at some logical point. So, as much as some folks would rather not think about it...
Wire up automated testing:
- PHPUnit
- PHPCS with Joomla Coding Standard
- Hook into Travis-CI
- PHPMD
Done
Testing framework is in and can run PHPCS and PHPMD now.
Did you manage to make it run on Travis ?
I get strange errors trying to install PHPMD using pyrus: https://travis-ci.org/elkuku/jissues/jobs/6899980
Also - I just wrote the first unit test. Any idea where to place them ? Maybe in /tests ?
I didn't turn on the Travis integration or test it. I'm still fighting with PHPCS for the CMS on Travis. I did run things locally (mostly) without issue; had to add some leading slashes to some of the file paths in the ruleset.xml file, but I have no clue what's right anymore with those things (what works on Jenkins isn't working locally for me).
Try installing PHPMD with pear instead of pyrus, it looks to be supported - http://about.travis-ci.org/docs/user/languages/php/#Installing-PEAR-packages
I'd say put the tests in a tests folder. Makes it easier for me to keep non-production code off the web space I've acquired.
-
Could we add
?