Looking forward to getting my hands on Espresso. Would be interested to get your thoughts on appium.
Me too, looking anxious to see how Espresso works!
Espresso has been released http://googletesting.blogspot.com/2013/10/espresso-for-android-is-here.html
Thanks for sharing this great article.
What do you do for testing the performance or responsiveness of an application? That becomes hard because it is dependent on the actual hardware and the internet connection.
Nice post. I'd be really keen to hear how google approaches cross device/browser testing. Its always a big pain point for many organisations, but I don't hear too much about successfully approaches, or whether this is actually a valuable activity given the variance that exists.
What about actual user functionality? How does the Google+ team test that?
Guys, do you plan to share monkey for iOS to the world :) ?Right now there are only two alternatives:AntEater https://www.redant.com/anteater/UI-AutoMonkey https://github.com/jonathanpenn/ui-auto-monkey
Hi Alexander,We are looking into opensource it in the near future, stay tuned.
Nice Article.Will this tool mitigate a challenge of asserting mobile app. UI with respect to different device screen sizes.
Should I use Robolectric for anything beyond unit test? If I use that, than do I still need Espresso? And do you know how "real" is Robolectric compared with real emulator? I am afraid that I have to fix problems that are Robolecric specific.
Hi，Greate Article.I was wandering if there is any advice about how to test sdk which has no user interface.For example, I have developed a tool which can get infomation about location，and other apps will use this as a ***.jar lib. Any advice?
Thumbs up..never try this but will follow the instruction it is very interesting...Thanks!
Hi! Is this article up-to-date? How do you test "in-the-wild"?
We are also following the same, not exactly but similar to this structure.
Hi all,I have question currently backend is not yet ready, And our plan to start frontend testing with stubs simulating the backend behavior.The question is should we do phase before regression for checking after removing the stubs and testing with real testdata the backends are working fine OR regression will be enough. And what about real testdata wasn't available so could we do regression with the same stubs of backends?
How do you cover below testing for Mobile Apps :1. Battery Drain2. Memory Testing3. Performance Testing(App Side)
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.