Access the full text.
Sign up today, get DeepDyve free for 14 days.
References for this paper are not available at this time. We will be adding them shortly, thank you for your patience.
CHA P TER 5 ■ ■ ■ On any automated testing project, if you have to write every line of code from scratch every time, you’ll never finish. If you start early in the project to identify tasks that can be written and stored as utilities and used repeatedly, it will save you time and prevent headaches. An additional benefit is that some of these utilities are usable on other projects. Remember from Chapter 1 that one of the goals of good software is reuse? Actually, the whole reason you are automating testing in the first place is to increase your testing capabilities with code and to avoid doing certain tests over and over manually, right? So, it makes sense to create pieces of code generic enough to be used more than once. In fact, it makes even more sense to create a reusable framework of test routines and utilities that you can use from test project to test project. These framework routines can include all of your favorite code for doing common tasks on a test project. Common tasks on a test project can include actual tests, but since those will often be very specific to your test
Published: Jan 1, 2006
Keywords: Access Modifier; Menu Item; Main Menu; Public Share; Calculator Accessory
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.