Home
Our Software Testing Process - every 6 hours!

Ok folks - a boring, yet vital topic. Software testing methodology!

The most important requirements for our platform is reliability - we have over 25,000 people relying on our engine on a daily basis. For our main client, GoGet, a single days outage can mean losses in the tens of thousands of dollars. It's enough to give you gray hair!

Our greatest challenge is being innovative whilst at the same time maintaining a reliable platform - how do we roll out cutting edge new features without running the risk of accidentally breaking the system?

Simply put - we test early, and test often. Our platform has over 250 tests that must be passed before a release is put into 'GO' state. In the old days, we used to sit and run through day after day of manual tests with bleeding eyes and damaged brains. (Our top bug-finders do get prizes though - we recently gave an IPad to our top BugFinder to encourage her to find more!).

Since 2009, we've used an improved methodology called 'Continuous Integration' - with an automated testing layer that checks the critical functions every 6 hours. For example, we know within hours if the 'make booking' function has been adversely affected by a piece of code someone has added (thereby breaking our test platform - not production!).

This means greater confidence in the quality of our software, faster deployment of good code, and continuous wins for our clients!

To find out more about continuous integration, see these links.

  • http://en.wikipedia.org/wiki/Continuous_integration
  • http://www.extremeprogramming.org/rules/integrateoften.html
  • Last Updated ( Monday, 17 September 2012 )
     
    Our Software Testing Process - every 6 hours!

    Ok folks - a boring, yet vital topic. Software testing methodology!

    The most important requirements for our platform is reliability - we have over 25,000 people relying on our engine on a daily basis. For our main client, GoGet, a single days outage can mean losses in the tens of thousands of dollars. It's enough to give you gray hair!

    Read more...
     
    Context Sensitive Help

    We added a context sensitive help Wiki to our backend for our administrators. It combines the flexibility of a wiki with the convenience of a page specific help button.

    Read more...
     

    FleetCutter