* [x] regonfigured the build matrix with more php jobs and a separate python job (we can add more python jobs later) * [x] run tests on travis' trusty beta container (it's closer to what we need anyway) * [x] install packages needed for analyzer tests in build env * [x] added docs on how to run nosetests locally * [x] don't run initctl in analyzer setup so setup can also be used on travis (and add it to the install script directly) * [x] ignore replaygain checks on travis (it has proven quite impossible to get the needed python-gi module to work in the provided virtualenv) I tried a lot of solutions to get the replaygain checks to run. I needed to decide that this has gone far enough, maybe someone who is more of a pythonista than me can take a crack at it and get it solved. Even without running those tests on CI/CD there are still plenty others. This PR only has parts of what are needed for getting python tests running on travis as per #15. I only took a quick shot at anything not analyzer and figured I would not be able to "fix" them without digging a bit deeper (ie. also getting rid of std_err_override). |
||
---|---|---|
.. | ||
README.txt | ||
TESTING.md |
README.txt
README ====== This directory should be used to place project specfic documentation including but not limited to project notes, generated API/phpdoc documentation, or manual files generated or hand written. Ideally, this directory would remain in your development environment only and should not be deployed with your application to it's final production location. Setting Up Your VHOST ===================== The following is a sample VHOST you might want to consider for your project. <VirtualHost *:80> DocumentRoot "/home/naomiaro/airtime/public" ServerName airtime.local # This should be omitted in the production environment SetEnv APPLICATION_ENV development <Directory "/home/naomiaro/airtime/public"> Options Indexes MultiViews FollowSymLinks AllowOverride All Order allow,deny Allow from all </Directory> </VirtualHost>