On Wed, 01 Oct 2014 23:13:25 +0200, Cédric Beust ♔ <[email protected]>
wrote:
So we went with JUnit 3.
I'm sorry.
It was a very prudential decision of you at the time, man. The real
question is why do they stick with JUnit 3 after so many years!! I mean,
why they at least didn't upgrade to JUnit 4?
For the rest, Rakesh, I do second the idea of keeping most of the code
Android independent, so you can test it as you like. It's what I did since
the beginning for my first project. If you also do a good separation of
concerns between the presentation and its controllers, possibly using a
pattern that minimizes/zeroes the logic in the presentation, you gain some
points. My suggested approach is also to keep presentation controller as
clean from Android code as possible, even though this requires some more
effort and it needs to be evaluated on a per-project basis. Of course this
won't solve the problem, because in the end you also need to test the
whole system... and yes, adb is not reliable, and there are the other
problems you mentioned, and you need to do some manual testing. But at
least you minimize the chances of finding bugs at this level and reduce
the number of test rounds.
--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - [email protected]
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/javaposse.
For more options, visit https://groups.google.com/d/optout.
