Cypht uses PHPUnit to run our unit tests, and Selenium for integration testing. I periodically update the HTML coverage report located here: /docs/test_coverage/index.html. Currently our unit tests only cover the application framework (all the code under "lib/"), and our Selenium tests are still pretty basic. We make use of the following services that generously provide access to Open Source projects:

Travis CI

https://travis-ci.org/jasonmunro/cypht/builds

Travis CI is a really cool continuous integration service that we use to re-run our unit and UI tests every time a change is pushed to Github. Our Travis build is 15 combinations, 5 versions of PHP (5.4, 5.5, 5.6, 5.7, 7.0, 7.1) with 3 different databases (Mysql, Postgresql, Sqlite). Since the build takes about 2 hours, I often cancel repeated runs when I'm doing a lot of pushing so I don't hammer the service too hard.

BrowserStack

https://www.browserstack.com/

BrowserStack is a cloud based Selenium grid we use to run our UI tests. We connect to it directly from Travis CI. Currently we test 5 browsers (Safari, IE, Edge, Firefox, and Chrome).

Coveralls

https://coveralls.io/github/jasonmunro/cypht

Coveralls.io provides access to the PHPUnit test coverage report, and is updated every time code is pushed to Github. It has some cool metrics to track unit test coverage over time, and in general is a nicer UI than the PHPUnit HTML report.

Scrutinizer

https://scrutinizer-ci.com/g/jasonmunro/cypht/

Scrutinizer is a static code analyzer with a lot of great options. It understands our doc-string format and provides additinal information about potential type mismatches, in addition to a number of other static checks. Currently I have it limited to the application framework (all the code under "lib/"). Like the Travis builds and Coveralls reports, a new analysis is run every time we push code to Github.