Version 21 (modified by Fran Boon, 11 years ago) ( diff )


Continuous Integration

Current Setup

CI Server's cron runs the tests every 6 hours

  • Using Web2Py from Tue Jan 15 22:23:00 2013
  • Using latest Trunk Eden
  • Using IFRC template
  • Using SQLite
  • Using Chrome

Results are stored as HTML files in the filesystem which can be accessed via the Eden instance under test:


  • Updates Web2Py to current Trunk (from
    • Currently disabled
  • Updates Eden to current Trunk (from
  • Cleans database & prepopulates
  • Runs Functional Tests (Selenium)
  • Runs Smoke Tests
  • Runs Roles Tests
    • Currently disabled
  • Mails out test results (using /usr/local/bin/

NB Tests require Python 2.7, so Pythonbrew is used to allow this to coexist with the system Python 2.6

To run the test suite manually:


Open another console then:


To just run smoke tests:

cd /home/web2py
xvfb-run -a python -S eden -M -R applications/eden/modules/tests/ -A --html-path /home/web2py/applications/eden/static/test_smoke/ --suite smoke --force-debug --link-depth 16 -V 4

Start Window based applications (x11):

  • If the GUI window of the application is of no interest to you:
    xvfb-run -a *test commands here*
    For example :
    xvfb-run -a python -S eden -M -R applications/eden/modules/tests/ -A -V 2
    Note: Xvfb basically makes a virtual display which isn't displayed anywhere. Xserver itself actually requires a real display
  • If you want to see the GUI interface of the application
    • If the machine you use to ssh into the server, has X Server installed, then you can access the GUI window by using the -X flag when loggin into the server
      ssh -X youraccount@
      And now, if you simply execute any application which has a Xserver attached to it, it will be displayed on your screen.

Plans for Future

  • Move mailing script out of a personal user directory
  • Move cron commands to system /etc/crontab rather than root's crontab
  • Fix Reporting of Smoke Tests
  • Enable Roles Tests & fix any issues which caused it to be disabled
  • Run Unit Tests
  • More templates (default, etc)
  • More databases
  • More browsers
  • Install an Eden instance to act as a CI server
    • Move the cron scripts to being run by Eden Scheduler
    • Have Eden manage the mailing of results & manage subscriptions
    • Have Eden store the results in the database for Graphical analysis
    • AUT should be on remote servers
      • Spawn AWS instances using
      • AMIs built for Cherokee/PostgreSQL & Apache/MySQL to speed-up bootstrapping of instances
      • Can do Performance Testing as well as other tests
    • This replaces the old install of Jenkins

Setup Notes & Discussions (to be ported to Wiki):

Attachments (4)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.