At Output42 we do projects for customers, often on legacy code and oddly enough they are happy to pay for us to test the changes. So, we do a good job on the enhancements and testing and before you know it they are back for more, Krrrching! You then do some more and test the changes and the changes you made previously, release it and they are happy, Krrrrching! and so the cycle repeats. However it all starts to fall apart when you have done this many times and the job of testing the changes gets to unmanageable, unprofitable proportions … gulp.

Enter automated testing.  At Output42 our testing team has settled on using seleniun as the framework for testing web applications. We will try and share the whole story, warts and all.

 

Comments are closed.