Android Testing - Getting Started with Espresso 2.0

In this video we cover how to set up your Android Studio environment to use Espresso 2.0. We talk about matchers, assertions and how to use them. We also demonstrate a simple TDD (Test Driven Development Method) implementation for the first test. At the end of this screencast you should be able to set up your Android Application with the Espresso Testing framework.
For more videos see www.caster.io or this CZcams channel: / @donnfelkeryt

[@VijayaPrakashKandel]

You just saved my tomorrow.

[@magosiatanska2867]

I am waiting for more advanced examples :)

[@tiwanakku]

Great stuff! I'm just starting with Espresso and this is exactly what I needed!

[@zebronicsjay]

+Martin Stefan Can continue test possible in android espresso?
Also in case of error can we implement error collector?

[@LogicPhalanx]

This is great ***** tons of useful information here.

[@regismaltais5743]

I will like to remote control with TeamViewer an Android TV box. The problem that I have is there is a popup on the Android TV that ask to push a button to allow the remote control. Does Espresso can look for the popup window and click on the Allow button for me ?

[@vipin_thegame]

Thank you! Nicely explained :)

[@akshatsharda8018]

Hey, nice video, but there is a problem that I'm facing with setting up the androidTest directory. Android studio doesn't recognize it as a test directory, and upon running a sample test, it reports 'no tests were found.' I also have a 'test' directory with unit test cases in it, but i did change the build artifact to Android Instrumentation Tests. The test directory is being detected properly.

[@dmitrykologrivko]

Thank you very much, good lesson

[@emmanouilkounalakis1952]

Great tutorial

[@bubblesDF]

Great tutorial thanks

[@VAdaihieph]

Thanks, very useful.

[@abzal9551]

where can i download the app for testing?

[@redelpedron325]

Thank you.

[@anilphilip546]

@donnfelker How to simulate the clicking of the application icon on the home screen? I do not want to run Activity Rule because I have more than one launchable Activity. I have 3 icons, actually. One for each Activity.

[@zebronicsjay]

Can continue test possible in android espresso?
Also in case of error can we implement error collector?
Please help me for the same.

[@VishnuTB7]

thank you

[@girijajoshi8911]

Hi, i am new to android app testing. I have ready developed app (no source code) just APK. Can i use Espresso to test UI? If not any other tool?

[@kem5134]

Thanks for the video. It was very helpfull. :)

[@hugovera1540]

Is there some source code somewhere? The app that is being tested is not being showed up

[@donnfelkeryt]

No. This video is very old and I’m not sure the code would even compile with the modern tooling anymore.

[@codingwithshamy1745]

why did you stop uploading more videos?

[@TheHagelberg]

could you show me code in class MainActivity and NavigationDrawerFragment?

[@9932shashank]

Hi Donn, is it possible to run Espresso tests without app development source code? I have a release apk file which i want to test with Espresso test. Is it possible to write it? if yes, can you give some pointers or github link please?

[@donnfelkeryt]

Check this link out: stackoverflow.com/a/18064368

[@yogeshranjitkar5299]

Can you please explain from where you copied the androidTestCompile and pasted it in dependencies..

[@Jackty89]

google.github.io/android-testing-support-library/docs/espresso/setup/index.html

[@philipyoung7034]

@@Jackty89 404 error: File not found

[@ThanhTranIT]

very useful so I hava just subscribed chanel :)

[@MrConkerLynch]

+Thanh Tran Hey Thanh just wondering where did you get ActivityRule.java? I cant find it on Jake's account

[@DannTeBg]

how to do that on a fragment?

[@MrNiceseb]

Please show Twitter login WebView Espresso example? Thanks

[@haonanzhao92]

Can you give us the link for activity rule, i found the link is not valid anymore

[@noodlesnsoup]

+Haonan Zhao add androidTestCompile 'com.android.support.test:rules:0.4' to your depdencies; afterwards you can use the ActivityTestRule imported from the JUnit Rules

[@FurociousN]

+Haonan Zhao gist.github.com/JakeWharton/1c2f2cadab2ddd97f9fb

[@philipyoung7034]

Yay! for Jake Wharton. His code is now part of the repository. "This test rule is now in the 'test-rules' support repository. Use that one!" Sad for us because this excellent tutorial is missing its key feature.
I found a clone of the ActivityRule.java file, but I cannot get it to work. "Cannot resolve symbol InstrumentationRegistry"

[@ColtWillcox]

I still don't understand the real life purpose of testing. :(

[@vankwisha]

So you don't release something with bugs lol

[@asdqwe4427]

VaNkWiShA something with less bugs.

[@meajudalimpeza5312]

I work in a company that every new release, we need to run the same test. This allows me to do it automatic, which is faster and more consistent.

[@marekkubacka315]

I work as Software Tester, and believe, there is meaning why to make testing manual or automatic

[@thomasnguyen6923]

Manual testing is usually for finding new bugs. Automation testing is for testing previous and new requirements automatically so we don't test non stop. Usually a dev doesn't have time to test extensively his code. That's what a tester is for.
For a small application (i.e. school homework), you don't need a tester. But when you deal with thousand of files, this can be time consuming and it is best to catch bugs before the customers experience them.

[@vishalkumarsinghvi]

cheet sheet in prezi:-prezi.com/piqd29upzrii