Harry, Vishal,
Same as John, I am very curious about how are you practically mocking up EO's, VO's or AM's, whatever Mocking framework.
I must say I've never used mocking in relation with ADF technology, but sometimes we've needed
STUBS to simulate a web service call, or a database package that wasn't created yet. But this is rather related to ADF integration with other technologies, then with ADF components directly.
I look forward to see a decent size ADF application written in Test Driven Development style, with JUnit tests over BC and developers writing-tests-first, before writing business logic. Not sure I will any time soon, since ADF Model layer is not Test-Driven-Development friendly I would dare saying. With such tight integration between ADF Faces and ADF BC, JUnit tests bring rather limited gain, since ADF Faces can control ( and change) the VO's queries or fetching behaviour. In order words, you can't really test your Business Logic in isolation, since you can't truly control the set of operations you expose to View Layer. Though, you can test SOME of the functionality like complex db functions or queries.
This is why we moved away from Unit Testing towards Automated Acceptance Testing, using Selenium and JUnit, where we test the whole functionality exposed in browser, rather than isolating modules.
Thanks,
Florin