Automated Testing

We use automated testing processes to check and re-check our client sites. These are automatic scripts that describe to a virtual user how the site should look and behave – eg “when you click on this you should see that”. These virtual users comprehensively run through thousands of different parts of the site to check that everything is working correctly.

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 GitHub 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.

Ben Still 07 Apr 2013

Testing web projects

One of the things we’ve started doing quite differently over the last few years is how we test our web projects

Ben Still 25 Sep 2012

Vulnerability scanning

Vulnerability scanning software Ruby on Rails analysis

Ben Still 28 Feb 2012

A look inside our Jenkins Pipeline – how we make reliable stuff

How we build relational trust; our integrated testing pipeline

Ben Still 24 Feb 2012

How a project gets tested and deployed with GitFlow

GitFlow is the way of the future. Find out why and how here.

Ben Still 31 Jul 2009

Multi-variate testing

Lately, we’ve been doing quite a bit of work on sites which involve multi-variate (MV) testing