The short answer to "Selenium seems like an alternative for HttpUnit or HtmlUnit" is a yes.
Without going into a long discussion, I have a Maven project containing all the business logic. That project contains the appropriate tests. The user interface project, using MyFaces in this case, only test the UI, not the business logic. The MyFaces project does include some Shale[1] and Selenium based testing. Shale based testing is very similar to jUnit testing and can be used to test manage beans. It can be include in the Maven build process. Selenium requires user interaction in the testing process. Their are services, like HostedQA [2], the can run a Selenium test as a part of the Maven build process. FYI: If you choose to use Selenium, I strongly suggest using the id attribute on any tag being test. This will make the test less brittle and more reliable. Paul Spencer [1] http://shale.apache.org/shale-test/index.html [2] http://www.hostedqa.com/ lightbulb432 wrote:
Thanks for those resources on Selenium, I'm going to look into it. Selenium seems like an alternative for HttpUnit or HtmlUnit, am I right? If so, I'm still confused about whether to test the HTML output in addition to the session beans, or whether testing any one of the two will do. I ask because generally the HTML output is generated from the interface published by the session beans. So would somebody using Selenium not test their session beans separately, because their correctness is being indirectly tested by testing the web output?
