On 15 Mar 2011, at 02:15, A. Elk wrote: > Good work. I have a couple of comments:
Glad you like it :-) > If you have POJOs in your code, you can test them with JUnit using a > standard mocking framework of your choice. The only limitations on > mocking are imposed by the Android system. That's true, of course. In our particular case, however, all of our non-Android-specific code is C++, so we have no Java code that doesn't talk to Android APIs. Our C++ code has extensive fully-automated unit and functional tests. We've found achieving the same level of test coverage for our Java code to be *extremely* difficult. Hopefully the techniques outlined on my blog will remedy that somewhat. > Without getting into too much detail, most of the objects in the > Android API can't be mocked. This is known. It's not meant to be test- > hostile, and it's not accidental. I always think that to get anything > useful in a finite amount of time, one has to make tradeoffs. That's clearly true, and I'm sure that the Android developers weren't deliberately trying to make Android test-hostile. Even if it *feels* like it sometimes :-) > I think the key thing is that you've produced something useful for > Android developers. I hope so! I'd be very interested to hear your, and others, feedback if/when you've had a chance to play with Borachio. It's still very young and I'm sure that there is much that could be improved. -- paul.butcher->msgCount++ Snetterton, Castle Combe, Cadwell Park... Who says I have a one track mind? http://www.paulbutcher.com/ LinkedIn: http://www.linkedin.com/in/paulbutcher MSN: [email protected] AIM: paulrabutcher Skype: paulrabutcher -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
