This article was originally published on LinkedIn Pulse. Read the full article here.
With ever shorter development and release cycles and a need to continuously deliver high quality software in an increasingly competitive market, fast feedback on software quality has become something that most software-producing organizations just can’t do without. Back in ‘the days’, automated tests written to obtain this fast feedback used to consist of either unit tests written and executed by developers, or end-to-end test scripts created and maintained by test automation engineers – all too often using the maintainability and reusability horror that is record and playback.
Since then, test automation has evolved from something considered an ‘extra’ into an indispensable factor in the software development and testing process. However, far though the field has come, there are still a number of fundamental concepts that are unknown to those involved in or relying on test automation. In this post, I’d like to try and shed a little light on some of them.