JMock is a library that supports test-driven development1 of Java2 code with mock objects3.
Mock objects help you design and test the interactions between the objects in your programs.
"JMock is a library that supports test-driven development of Java code with mock objects.
Mock objects help you design and test the interactions between the objects in your programs.
The jMock library:
makes it quick and easy to define mock objects, so you don't break the rhythm of programming.
lets you precisely specify the interactions between your objects, reducing the brittleness of your tests.
works well with the autocompletion and refactoring features of your IDE
plugs into your favourite test framework
is easy to extend."
While you need basic functionalities, everything is fine. When you need to modify the component (which is configurable, right?) you are facing the problems
EXTREMELY idiotic thing - because JSF has their famous lifecycle with lots of magic phases, some backing bean getters are called multiple times!
Back button problem.
Unreadable URLs. JSF always does the POST.
JSF is submitting a form on itself so it could call a backing bean method to handle an event. Of course, if you have a request, there is unnecessary repeated initialization, getter calls, postconstruct etc
Reusability? Good joke…
JSF - you are FIRED!
IDE support
Development of custom component? No way, extremely complicated. Extensible? In the movie, maybe…