I very much want to do things the "right" way, and that means testing. Yet with all the options out there (SeamTest, JSFUnit, Selenium) as well as all the various categories of testing (unit, integration, acceptance, performance), I am really confused as to which serves which purpose.
It seems like JSFUnit makes SeamTest integration tests unnecessary. SeamTest unit tests though are still cool. It also seems like JSFUnit does what Selenium would do (acceptance testing) if Selenium could understand RichFaces components. Still, Selenium does have a format that normal people can understand.
I can continue to ramble, but I would rather have some insight into how these various testing options fit into the various categories of testing. For example, could I legitimately use SeamTest for unit testing and JSFUnit for integration, acceptance, and performance testing?
I've never been convinced by using SeamTest for unit testing.
Selenium and JSFUnit are a bit different - one is scriptable, one isn't.
We plan to use JSFUnit for some integration tests in the future, and Selenium for release testing.
Try to grab Stan Silvert's JSFUnit presentation, he gives a good overview of testing options