Welcome,
New User!
New User!
Unit Testing in Java
By: Johannes LinkImprint: Morgan Kaufmann
Format: Adobe Encrypted (DRM)
Earn $0.50 - Write a Review »
Our Price
$37.49
Reward Money:
$0.00
Software testing is indispensable and is one of the most discussed topics in software development today. Many companies address this issue by assigning a dedicated software testing phase towards the end of their development cycle. However, quality cannot be tested into a buggy application. Early and continuous unit testing has been shown to be crucial for high quality software and low defect rates. Yet current books on testing ignore the developer's point of view and give little guidance on how to bring the overwhelming amount of testing theory into practice. Unit Testing in Java represents a practical introduction to unit testing for software developers. It introduces the basic test-first approach and then discusses a large number of special issues and problem cases. The book instructs developers through each step and motivates them to explore further.
*Shows how the discovery and avoidance of software errors is a demanding and creative activity in its own right and can build confidence early in a project.
*Demonstrates how automated tests can detect the unwanted effects of small changes in code within the entire system.
*Discusses how testing works with persistency, concurrency, distribution, and web applications.
*Includes a discussion of testing with C++ and Smalltalk.
See more like this in our Computers eBooks section
Share your thoughts on the Unit Testing in Java Computers eBook with others!
| Title of Computers eBook: Unit Testing in Java | |
| Release Date: 05-20-2003 | |
| Publisher: Morgan Kaufmann |
This eBook download is available in the following formats:
| Parent title | Unit Testing in Java |
|---|---|
| Encrypted (DRM) | Yes |
| SKU | 9780080520179 |
| File size | 16664 |
| Security | n/a |
| Printing | Not allowed |
| Copying | Not allowed |
| Read aloud | No Sys requirements Download reader |
| Devices | Samsung Tablet, Apple Ipad & Iphone, Barnes & Noble Nook, Kobo eReader, Aluratek Libre, Iliad, Nokia, Blackberry, Hanlin |
| Note | Excellent navigation features are available via Adobe such as bookmarks and a quick access table of contents. Text search is easily accessible. An Adobe DRM-protected file is different than a pdf file in that it uses Adobe DRM (Digital Rights Management) technology, which authors and publishers use to protect their content from illegal online distribution and to set certain privileges such as restrictions on copying and printing. |
Unit Testing in Java
Chapter One
Introduction
Testing is important. All software developers know it, but (hardly) anyone does it. Luckily, you have bought this book and therefore don't belong to this ignorant crowd ;-)
There are many reasons for the poor interest of programmers in the quality of their own products. Education plays an important role. Academically educated computer scientists hear of the fact that software has to be tested mostly as a theoretical topic within their two-semester software course. The autodidacts among programmers normally find nothing in their textbooks and programming books, except a note that programs should "of course" be thoroughly tested. Only you won't find how and why in these books, with a few praiseworthy exceptions, like those by Hunt and McManus and Larman and Gutherie.
Eventually, developers build their own stock of prejudices and reasons reinforcing their dislike for testing. Here a few examples.
"I have no time for testing."
This frequently heard sentence assumes that testing takes a great deal of time. If you believe this, you will be caught in a vicious circle. The greater the time pressure, the fewer tests; the fewer tests, the more unstable your code. The more unstable your code, the more error reports will fly in from customers. The more error reports, the more debugging time will be required. The more debugging time, the greater the time pressure....
On the other hand, if you believe that tests stabilize your code, then this vicious circle will turn into an open spiral. The more stable your code, the less debugging time will be required. The less debugging time, the mo
...
