LOGIN | REGISTER NOW | SUBSCRIBE
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 7/1/2009 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
Is the mystery Borland suitor Serena?
Borland software is considering an offer from another company after a preliminary deal with MicroFocus. Is Serena the new company?
06/30/2009 01:55 PM EST

Windows 7 - An eBayer's dream product?
Windows 7 pre-orders can make people money on eBay.
06/29/2009 03:48 PM EST

Know thine cloud provider
Cloud computing require companies to understand compliance and regulation. Third parties will play a big role in regulated industries.
06/29/2009 02:58 PM EST

 

Microsoft Worldwide Partner Conf.
7/13/2009 to 7/16/2009
New Orleans
Microsoft

OSCON (Open Source Convention)
7/20/2009 to 7/24/2009
San Jose
O'Reilly Media

XBRL Technology Workshop & Summit
7/28/2009 to 7/30/2009
Santa Clara
XBRL US

ACM SIGGRAPH
8/3/2009 to 8/7/2009
New Orleans
ACM SIGGRAPH

OpenSource World (formerly LinuxWorld)
8/12/2009 to 8/13/2009
San Francisco
IDG World Expo


 
print Printable version 
Most Read Latest News Blog Resources
Kapow automates website data retrieval
Kapow Technology's Web Data Server 7.0 can be used to create modules that navigate through...

Oracle's Fusion 11g lays groundwork for ERP platform
Fusion's components are standards-based and integrated, but some abilities are lost if non...

COBOL’s future lies in the clouds
After 50 years of use in businesses, COBOL is still lingering around mainframes. But the s...

Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter

AgitarOne: Unit Tests For Old Code


By Alex Handy
December 1, 2006 — 
By now, every good developer knows that unit testing is of primary importance to the development process. However, Jerry Rudisin, CEO and president of Agitar Software, said that there’s one area of development that is perpetually left out of the unit testing tumult: inherited code.

“One of the things that got in the way of people [trying to do unit testing] has been the fact that they had this really nasty mass of legacy code written in Java that they knew they wanted to start modifying and enhancing, but they didn’t want to touch it because they had no unit tests for it,” said Rudisin.

To address the situation, Agitar in mid-November released AgitarOne, a new product that includes all of Agitar’s previous software offerings mixed together with server-side JUnit test generation.

“Unleash AgitarOne on your legacy code, and it will go through and generate a good set of JUnit tests,” Rudisin said. “They’re not as good as hand-generated JUnit tests on original code, but they serve as a really useful set of regression tests.”

AgitarOne includes all of Agitator 3.0’s standard features: a dashboard for viewing code coverage, support for exploratory testing and code standards enforcement. But AgitarOne’s server-side approach to the testing process brings some new abilities to the mix. For starters, AgitarOne automatically installs the open-source tool Ant to give developers the ability to do continuous integration testing.

But the real reason for running AgitarOne on the server and not on the desktop, said Rudisin, is that the product’s automated test generation is very CPU-intensive. Thus, off-loading automated JUnit test generation onto the server frees up desktops to deal with standard daily tasks. Rudisin added that AgitarOne is capable of utilizing multiple CPUs and servers for its computations.

A standard installation of AgitarOne costs around US$50,000, said Rudisin. The server-side tool is accessed through Eclipse plug-ins, which are included in the product. Developers simply install the AgitarOne plug-in, and are then able to add unit tests through the Eclipse project view. Tests can be generated on a small scale—testing a single class—or a large scale—testing an entire project. All of these tests are generated from scratch as needed.

And while the tests generated by AgitarOne will never be better than hand-coded unit tests written at the same time tested code is completed, the tool automatically generates its tests based on the user’s desired code coverage requirements. That, said Rudisin, means code with absolutely no unit tests can be 70 percent covered from top to bottom with only a few mouse clicks and some dedicated server-side CPU time.


Share this link: http://www.sdtimes.com/link/29870
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading