automated testing


We use an automated testing process to check our work. These scripts are then run via Continuous Integration to ensure that any new work doesn't break existing features.

When testing a web project, we check for four key things:

  1. Does it work correctly?
  2. Does it look right?
  3. Is everything else still working?
  4. Are there any security holes?

Each time a developer makes a change, it is sent to the lead developer for peer review. Once approved it is added to the code repository, which triggers a series of automated tests to check against all of the above criteria. By carefully describing how the site should function and then testing those functions, any issues are immediately picked up and resolved.