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 ProgrammingThe Basics of Storing Test Data

A Tester’s Guide to .NET Programming: The Basics of Storing Test Data CHA P TER 3 ■ ■ ■ The Basics of Storing Test Data In Chapter 2, you learned about the three different kinds of .NET applications you can choose to write your testware. In each application, you wrote the results of your tests out to either a message box or a label. This kind of test reporting—while quick and simple—isn’t very prac- tical for long-term projects. What if you want to run your tests overnight? Also, you will need to provide test result documentation to management and customers, so you’ll have to be able to store this data somehow and provide reports. And what about other kinds of data besides test results? For example, say you want to store some settings for your tests to compare from one test run to the next, like the last date they were run or who ran them? So, there are all kinds of data that you’ll need to work with on a test project, and controlling and accessing this data is an essential part of your job. Think about it, what does it matter if you find bugs if you can’t prove that you did? In fact, some of the most important http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png

A Tester’s Guide to .NET ProgrammingThe Basics of Storing Test Data

Download PDF
47 pages

Loading next page...
 
/lp/springer-journals/a-tester-s-guide-to-net-programming-the-basics-of-storing-test-data-0SqeFRpVAG

References (0)

References for this paper are not available at this time. We will be adding them shortly, thank you for your patience.

Publisher
Apress
Copyright
© Apress 2006
ISBN
978-1-59059-600-5
Pages
39 –86
DOI
10.1007/978-1-4302-0116-8_3
Publisher site
See Chapter on Publisher Site

Abstract

CHA P TER 3 ■ ■ ■ The Basics of Storing Test Data In Chapter 2, you learned about the three different kinds of .NET applications you can choose to write your testware. In each application, you wrote the results of your tests out to either a message box or a label. This kind of test reporting—while quick and simple—isn’t very prac- tical for long-term projects. What if you want to run your tests overnight? Also, you will need to provide test result documentation to management and customers, so you’ll have to be able to store this data somehow and provide reports. And what about other kinds of data besides test results? For example, say you want to store some settings for your tests to compare from one test run to the next, like the last date they were run or who ran them? So, there are all kinds of data that you’ll need to work with on a test project, and controlling and accessing this data is an essential part of your job. Think about it, what does it matter if you find bugs if you can’t prove that you did? In fact, some of the most important

Published: Jan 1, 2006

There are no references for this article.