{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Evening l夕情丶 的问题《Android Instrumentation Tests Stuck “Running Tests》','https://www.manongdao.com/q-850283.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I use Android Espresso Tests with latest Android Studio 2.1.2 and Tests are running ok but it does not seems like the standalone test app returns back the results to reflect back to Android Studio and it shows Running Tests Forever
相关问题
- NullPointerException in RecyclerViewMatcher when t
- “java.lang.RuntimeException: Could not launch inte
- android.support.test.espresso.PerformException: Er
- How to surpass location enabler dialogue in UI tes
- Clear database before testcase espresso
相关文章
- Using proguard with espresso/androidTest
- Flaky Android Espresso Test - Snackbar
- Espresso test Fail
- How to select a specific Tab position in Tab Layou
- Espresso: AppNotIdleException
- Editing AndroidManifest.xml in Gradle task process
- Espresso Injecting a Mock Presenter Object
- Android Espresso ListView click item
You have to try removing testCoverageEnabled option from build.gradle file if it's there. possible duplicate Gradle build tool long for android Tests
I realize this is an old question, but I just ran into this and didn't see any other search results that had the same problem.
In my case, this was caused by the code under test having a stack overflow exception, which it seems that the test runner failed to handle. I was only able to figure it out by looking at the "Android Monitor" and looking in the logcat.
So if you get to the point where AS just sits at "running test" forever, you might want to look in logcat for an exception that the test runner couldn't handle.
In case this helps anyone. In my case, I was setting the idle state wrongly(false instead of true) after doing a background task, so espresso was stuck thinking that was idle.