| 3 | CI Server results: |
| 4 | * http://82.71.213.53/eden/admin/result |
| 5 | |
| 6 | Setup Notes & Discussions (to be ported to Wiki): |
| 7 | * https://docs.google.com/document/d/1T29cF3kkK4lIAVdiATfE8a-tLm_Tyh3_dIh6FJWY7sU/edit |
| 8 | |
| 9 | To run the test suite manually: |
| 10 | {{{ |
| 11 | sudo sh /etc/cron.custom/web2pystarter |
| 12 | }}} |
| 13 | Open another console then: |
| 14 | {{{ |
| 15 | sudo sh /etc/cron.custom/testsuite |
| 16 | }}} |
| 17 | This first updates Eden and Web2py from Github, then runs the functional tests followed by smoke tests. |
| 18 | |
| 19 | To just run smoke tests: |
| 20 | {{{ |
| 21 | cd /home/web2py |
| 22 | xvfb-run -a python web2py.py -S eden -M -R applications/eden/modules/tests/suite.py -A --html-path /home/web2py/applications/eden/static/test_smoke/ --suite smoke --force-debug --link-depth 16 -V 4 |
| 23 | }}} |
| 24 | |
| 25 | We also have an install of [SysAdmin/Jenkins Jenkins] which could be configured to run this. |
| 26 | - or we could setup an Eden instance to manage this via Scheduler for more control & storing results in a database for graphical reports |