Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

A Tester’s Guide to .NET ProgrammingCreating a Testing Framework

A Tester’s Guide to .NET Programming: Creating a Testing Framework 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 http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png

A Tester’s Guide to .NET ProgrammingCreating a Testing Framework

Loading next page...
 
/lp/springer-journals/a-tester-s-guide-to-net-programming-creating-a-testing-framework-jMx1RLH4Ai
Publisher
Apress
Copyright
© Apress 2006
ISBN
978-1-59059-600-5
Pages
139 –184
DOI
10.1007/978-1-4302-0116-8_5
Publisher site
See Chapter on Publisher Site

Abstract

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

There are no references for this article.