在我的测试中,我有一个阶段,按下按钮后,应用程序会执行大量异步计算并向云服务发出请求,之后会显示某个视图。
是否可以使用Espresso的class Game():
def __init__(self,window):
self.Window = window
def print_UI(self,*Args, **Kwargs):
self.Window.setup.output.insertPlainText(*Args, **Kwargs)
def print_label(self,*Args, **Kwargs):
self.Window.label.setText(*Args, **Kwargs)
def test(self):
self.print_label("HI")
实施来等到某个视图出现?
我已经阅读了答案here,而评论似乎暗示您可以使用IdlingResource
,但我不明白如何。 Espresso似乎没有任何内置的方法来处理长时间的操作,但是必须编写自己的等待循环就像是一个黑客。
任何解决这个问题的方法,或者我应该像链接线程中的答案那样做?
答案 0 :(得分:8)
Atte Backenhof的解决方案有一个小错误(或者我可能不完全了解其逻辑)。
getView 应该返回null而不是抛出异常以使IdlingResources工作。
以下是带有修正的Kotlin解决方案:
/**
* @param viewMatcher The matcher to find the view.
* @param idleMatcher The matcher condition to be fulfilled to be considered idle.
*/
class ViewIdlingResource(
private val viewMatcher: Matcher<View?>?,
private val idleMatcher: Matcher<View?>?
) : IdlingResource {
private var resourceCallback: IdlingResource.ResourceCallback? = null
/**
* {@inheritDoc}
*/
override fun isIdleNow(): Boolean {
val view: View? = getView(viewMatcher)
val isIdle: Boolean = idleMatcher?.matches(view) ?: false
if (isIdle) {
resourceCallback?.onTransitionToIdle()
}
return isIdle
}
/**
* {@inheritDoc}
*/
override fun registerIdleTransitionCallback(resourceCallback: IdlingResource.ResourceCallback?) {
this.resourceCallback = resourceCallback
}
/**
* {@inheritDoc}
*/
override fun getName(): String? {
return "$this ${viewMatcher.toString()}"
}
/**
* Tries to find the view associated with the given [<].
*/
private fun getView(viewMatcher: Matcher<View?>?): View? {
return try {
val viewInteraction = onView(viewMatcher)
val finderField: Field? = viewInteraction.javaClass.getDeclaredField("viewFinder")
finderField?.isAccessible = true
val finder = finderField?.get(viewInteraction) as ViewFinder
finder.view
} catch (e: Exception) {
null
}
}
}
/**
* Waits for a matching View or throws an error if it's taking too long.
*/
fun waitUntilViewIsDisplayed(matcher: Matcher<View?>) {
val idlingResource: IdlingResource = ViewIdlingResource(matcher, isDisplayed())
try {
IdlingRegistry.getInstance().register(idlingResource)
// First call to onView is to trigger the idler.
onView(withId(0)).check(doesNotExist())
} finally {
IdlingRegistry.getInstance().unregister(idlingResource)
}
}
UI测试中的用法:
@Test
fun testUiNavigation() {
...
some initial logic, navigates to a new view
...
waitUntilViewIsDisplayed(withId(R.id.view_to_wait_for))
...
logic on the view that we waited for
...
}
重要更新:IdlingResources的默认超时为30秒,它们不会永远等待。要增加超时,您需要在@Before方法中调用它,例如:
IdlingPolicies.setIdlingResourceTimeout(3, TimeUnit.MINUTES)
答案 1 :(得分:2)
您的IdlingResource可能如下所示:
import android.support.test.espresso.IdlingResource;
import android.support.test.espresso.ViewFinder;
import android.support.test.espresso.ViewInteraction;
import android.view.View;
import org.hamcrest.Matcher;
import java.lang.reflect.Field;
import static android.support.test.espresso.Espresso.onView;
public class ViewShownIdlingResource implements IdlingResource {
private static final String TAG = ViewShownIdlingResource.class.getSimpleName();
private final Matcher<View> viewMatcher;
private ResourceCallback resourceCallback;
public ViewShownIdlingResource(final Matcher<View> viewMatcher) {
this.viewMatcher = viewMatcher;
}
@Override
public boolean isIdleNow() {
View view = getView(viewMatcher);
boolean idle = view == null || view.isShown();
if (idle && resourceCallback != null) {
resourceCallback.onTransitionToIdle();
}
return idle;
}
@Override
public void registerIdleTransitionCallback(ResourceCallback resourceCallback) {
this.resourceCallback = resourceCallback;
}
@Override
public String getName() {
return this + viewMatcher.toString();
}
private static View getView(Matcher<View> viewMatcher) {
try {
ViewInteraction viewInteraction = onView(viewMatcher);
Field finderField = viewInteraction.getClass().getDeclaredField("viewFinder");
finderField.setAccessible(true);
ViewFinder finder = (ViewFinder) finderField.get(viewInteraction);
return finder.getView();
} catch (Exception e) {
return null;
}
}
}
然后,您可以创建一个等待视图的辅助方法:
public void waitViewShown(Matcher<View> matcher) {
IdlingResource idlingResource = new ViewShownIdlingResource(matcher);///
try {
IdlingRegistry.getInstance().register(idlingResource);
onView(matcher).check(matches(isDisplayed()));
} finally {
IdlingRegistry.getInstance().unregister(idlingResource);
}
}
最后,在你的测试中:
@Test
public void someTest() {
waitViewShown(withId(R.id.<some>));
//do whatever verification needed afterwards
}
您可以通过让IdlingResource等待任何条件来改进此示例,而不仅仅是为了可见性。
答案 2 :(得分:0)
我从Anatolii那里获得了灵感,但是我没有使用View.class中的方法,而是只使用ViewMatchers。
/**
* {@link IdlingResource} that idles until a {@link View} condition is fulfilled.
*/
public class ViewIdlingResource implements IdlingResource {
private final Matcher<View> viewMatcher;
private final Matcher<View> idleMatcher;
private ResourceCallback resourceCallback;
/**
* Constructor.
*
* @param viewMatcher The matcher to find the view.
* @param idlerMatcher The matcher condition to be fulfilled to be considered idle.
*/
public ViewIdlingResource(final Matcher<View> viewMatcher, Matcher<View> idlerMatcher) {
this.viewMatcher = viewMatcher;
this.idleMatcher = idlerMatcher;
}
/**
* {@inheritDoc}
*/
@Override
public boolean isIdleNow() {
View view = getView(viewMatcher);
boolean isIdle = idleMatcher.matches(view);
if (isIdle && resourceCallback != null) {
resourceCallback.onTransitionToIdle();
}
return isIdle;
}
/**
* {@inheritDoc}
*/
@Override
public void registerIdleTransitionCallback(ResourceCallback resourceCallback) {
this.resourceCallback = resourceCallback;
}
/**
* {@inheritDoc}
*/
@Override
public String getName() {
return this + viewMatcher.toString();
}
/**
* Tries to find the view associated with the given {@link Matcher<View>}.
*/
private static View getView(Matcher<View> viewMatcher) {
try {
ViewInteraction viewInteraction = onView(viewMatcher);
Field finderField = viewInteraction.getClass().getDeclaredField("viewFinder");
finderField.setAccessible(true);
ViewFinder finder = (ViewFinder) finderField.get(viewInteraction);
return finder.getView();
} catch (Exception e) {
throw new RuntimeException(e);
}
}
}
以及如何在测试用例中使用惰轮,我将ViewMatchers.isDisplayed()传递给惰轮中的预期条件。
private void waitUntilViewIsDisplayed(Matcher<View> matcher) {
IdlingResource idlingResource = new ViewIdlingResource(matcher, isDisplayed());
try {
IdlingRegistry.getInstance().register(idlingResource);
// First call to onView is to trigger the idler.
onView(withId(0)).check(doesNotExist());
} finally {
IdlingRegistry.getInstance().unregister(idlingResource);
}
}
使用此方法,您可以将任何Matcher.class传递给ViewIdlingResource构造函数,以作为通过viewMatcher参数找到的视图的必要条件。
答案 3 :(得分:-1)
要等待视图显示并可以对其执行操作。您可以使用此方法:
private const val sleepTime = 1000L
private const val maximumWaitedTime = 10000L // maximum waited time in milliseconds to wait a view visible
fun waitViewVisible(viewInteraction: ViewInteraction?, block: (() -> Unit)? = null) {
waitAssertView(viewInteraction, ViewAssertions.matches(isDisplayed()), block)
}
fun waitViewGone(viewInteraction: ViewInteraction?, block: (() -> Unit)? = null) {
waitAssertView(viewInteraction, ViewAssertions.matches(not(isDisplayed())), block)
}
fun waitAssertView(viewInteraction: ViewInteraction?, assertion: ViewAssertion?, block: (() -> Unit)? = null) {
if (viewInteraction == null || assertion == null) throw NullPointerException()
val startedTime: Long = System.currentTimeMillis()
var elapsedTime: Long = 0
var isVisible = false
do {
isVisible = runCatching {
viewInteraction.check(assertion)
}.isSuccess
if (isVisible) break
Thread.sleep(sleepTime)
elapsedTime = System.currentTimeMillis() - startedTime
} while (elapsedTime <= maximumWaitedTime)
if (!isVisible) throw TimeoutException("Waited time exceed the maximum waited time")
block?.invoke()
}