Driven by Tests... hopefully

Published:
Reading time:
About 1 min

A little late to the test driven side, I am, but I have played with JUnit for a while now. What I’m looking for is best practices to continue this implementation a little further. After some brief research, I have settled on the following setup for our tests:

Unit Testing
JUnit - obviously for unit testing POJO’s
-> Cactus - for server side unit testing of ejb’s
-> Strutstestcase - for unit testing Action classes. This I’m unsure of, but will look at Raible’s project for direction.

Functional/Acceptance Testing
HttpUnit - Http/Html driven tests
-> JWebUnit - Extension driven by code
-> Canoo Webtest - Extension driven by XML

Anyway, if you have any direction for me, please advise!