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:
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
One of the things we’ve started doing quite differently over the last few years is how we test our web projects
Ben Still 28 Feb 2012
How we build relational trust; our integrated testing pipeline
Ben Still 24 Feb 2012
GitFlow is the way of the future. Find out why and how here.