Abstract
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 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 we are automating testing in the first place is to increase our 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.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2001 Mary Romero Sweeney
About this chapter
Cite this chapter
Sweeney, M.R. (2001). Creating Test Utilities. In: Visual Basic for Testers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-1138-9_5
Download citation
DOI: https://doi.org/10.1007/978-1-4302-1138-9_5
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-893115-53-8
Online ISBN: 978-1-4302-1138-9
eBook Packages: Springer Book Archive