The Disco Blog

Believe it or not, there are numerous Struts applications alive today. They may not be the hippest things going, but they have business value so they’re in no hurry to go anywhere, at least until the cost to maintain them supersedes the cost to rewrite them. Until that point, it makes copasetic sense then to roll up your sleeves and test those applications so as to reduce the risk of introducing defects as modifications are made, right?

“Testing Struts legacy apps” is the latest article in IBM developerWork’s series “In pursuit of code quality”, which focuses on using the StrutsTestCase framework, in concert with DbUnit, to facilitate testing those omniscient Struts Action classes. As always, feel free to let it all hang out at the “Improve Your Java Code Quality” forum!

For additional resources on testing Struts applications see:

• StrutsTestCase simplifies the development process (DeveloperWorks, 01/05)
• Unit Test Your Struts Application (OnJava, 09/04)
• StrutsTestCase: The Tool for Struts Unit testing (Java Boutique)
• Component test repeatability (The Disco Blog, 02/06)

For additional resources on using DbUnit see:

• Effective Unit Testing with DbUnit (OnJava, 01/04)
• Practically Groovy: Of MOPs and mini-languages This article shows how to use DbUnit with Groovy (DeveloperWorks, 08/05)
• Isolated unit testing of persistence with Derby (DeveloperWorks, 11/05)
• Data diff’n with DbUnit (The Disco Blog, 07/06)

Trackback this Post | Feed on comments to this Post