Getting Automated Testing Under Control
Testing of systems is probably the most difficult task there is in IT -- especially if you want to execute the tests automatically. We make our living running test projects for customers, and have experienced many of the potential problems in testing and test automation ourselves:
- Testing costs time and money (usually during the end phase of a development project, when such time and money is least available)
- Manual execution of test cases is often a tedious and error-prone task (especially when tests have to be repeated on successive versions of a system)
- Automated tests tend to be very sensitive to changes in the target systems interface
- It can be difficult for outsiders to get a clear overview of what is being tested (especially when using automation scripts that non-IT people find hard to understand)
During the years we have evolved an approach to counter these issues. Although you shouldn't regard it as a "silver bullet," we think it can be very practical; we would like to use this article to share it with you. The approach is marketed under the name TestFrameTM, but you can easily apply the techniques and principles outlined in this article yourself.
View Entire Paper | Previous Page | White Papers Search
If you found this page useful, bookmark and share it on:
If you are familiar with RSS feeds, you can also sign up for our free blog feed. Our RSS feed is updated in real-time while our newsletter is updated daily.
