Ten best practices for Java automated testing
Stories Columns Opinions Resources
Preflight builds spread wings for smoother projects
Developers are increasingly turning to preflight builds, allowing them to experiment with ...
|
Coverity creates program to enforce code adherence
The Architecture Analyzer uses mapping technology from the company's Software DNA static a...
|
QCon 2008 features domain-driven development
This year's QCon invites speakers like Eric Evans and Dan North to talk about domain-drive...
|
.NET similarities prove golden for Silverlight
Microsoft has focused on making Silverlight 2 symmetric with the .NET platform, and that h...
|
SOA Watch: New economic realities
In the current economic downturn, agile programming and SOA are attractive options that bu...
|
Integration Watch: A new twist on threads
The key to raising the efficiency of multiprocessors is to shrink the overall workload by ...
|
Integration Watch: The Return of NetRexx?
Java scripting languages are seeing a surge in popularity, with NetRexx looking particular...
|
Windows & .NET Watch: Transaction crowd gets a boost
With multicore chips becoming the standard for processors, the need for a flexible, usable...
|
From the Editors: Election should shake up JCP
Rod Johnson has the right ideas for opening up the Java Community Process, and he may be a...
|
Letters to the Editor: Sun gives REST, SOAP choice
A reader takes issue with a headline on our story about Sun working with REST along with S...
|
Guest View: Be smart and lazy
The optimal solution for problems is the simplest one, so always aim to streamline your ap...
|
Zeichick's Take: From EXEC to EXEC 2 to REXX to NetRexx
Andrew Binstock's column last week, "The Return of NetRexx," brought back some fond memori...
|
Advanced Corda CenterView™ Data Visualization for the BusinessObjects™ Intelligence Platform
Corda Technologies presents a white paper on pervasive BI. The BusinessObjects business in...
|
From Mobile to SOA: A Guide for Optimized Application Deployment
Customer need has driven the emergence of multiple computing tiers. Today’s application d...
|
e-Kit: Web Application Security
Is your network secure? What about your web applications.
If IT security is your top p...
|
Practical tips for saving money on code maintenance
If software design is expensive, well, code maintenance is even more so. When you look...
|
By Lisa L. Morgan
April 1, 2008 —
Consultants and vendors have identified best practices for Java automated testing:
1. Test early and often. Bugs detected early are a lot cheaper to fix than those discovered in production or deployment.
2. Unit-test your development code to ensure it does what it’s supposed to do. No one knows your code better than you do.
3. Understand the costs and benefits of manual testing before you start automating tests. Otherwise, it would be virtually impossible to measure ROI.
4. Understand what level of test coverage you should have and are getting. There’s no such thing as 100 percent coverage using manual or automatic tests.
5. Understand which metrics matter. There are more available than actually matter to your project.
6. Use manual and automated tests where they make sense. This will save you time and money over the long term.
7. Focus on test design, not tools. Tests should be based on software requirements, not product features.
8. Build reusable test scripts. Both development and test code should be reusable.
9. Don’t forget that requirements are critical to validation. If you don’t understand what your code is supposed to do, it’s hard to prove it’s working properly.
10. Don’t give up your code reviews. Automated testing is no substitute.
Related Search Term(s): Java
Share this link: http://www.sdtimes.com/link/31872