Reputation: 30581
I have an instance where a couple buttons are shown and hidden depending on which page in a ViewPager is being shown. The are shown and hidden with Animators. Is there a way to check for/delay unit testing until this has been completed?
I'm using Robolectric since that's probably relevant. I tried calling Robolectric.runUiThreadTasksIncludingDelayedTasks();
but this didn't seem to fix anything.
The animation code is as follows:
public static void regularFadeView(final boolean show, final View view) {
view.animate()
.setInterpolator(mDecelerateInterpolator)
.alpha(show ? 1 : 0)
.setListener(new SimpleAnimatorListener() {
@Override
public void onAnimationStart(Animator animation) {
if (show) view.setVisibility(View.VISIBLE);
}
@Override
public void onAnimationEnd(Animator animation) {
if (!show) view.setVisibility(View.INVISIBLE);
}
})
.start();
}
Upvotes: 5
Views: 5167
Reputation: 1741
Here I put my solution based on ValueAnimator
classes. I use mockk library.
fun mockObjectAnimators() {
mockkStatic(ObjectAnimator::class)
val targetSlot = slot<Any>()
val propertySlot = slot<String>()
every {
ObjectAnimator.ofFloat(capture(targetSlot), capture(propertySlot), *anyFloatVararg())
} answers {
spyk(
ObjectAnimator().apply {
target = targetSlot.captured
duration = 0L
setPropertyName(propertySlot.captured)
}
).also { spy ->
every { spy.start() } answers {
spy.listeners.forEach { it.onAnimationStart(spy) }
spy.listeners.forEach { it.onAnimationEnd(spy) }
}
every { spy.setDuration(any()) } answers { spy }
}
}
}
For ViewPropertyAnimator
you could try similar approach
Upvotes: 0
Reputation: 30581
I ended up creating an AnimationUtility interface and a real and fake implementations. The fake implementation immediately set the view to visible/hidden instead of doing the animation. I dynamically inject the real/fake one depending on the proper context.
Upvotes: 3
Reputation: 2883
I think you could solve this problem rearranging the approach. This is, by extracting the SimpleAnimatorListener to a protected variable, and then unit test based on that. Something like:
@VisibleForTesting
SimpleAnimatorListener getAnimationListener(boolean show, View view) {
return new SimpleAnimatorListener() {
@Override
public void onAnimationStart(Animator animation) {
if (show) view.setVisibility(View.VISIBLE);
}
@Override
public void onAnimationEnd(Animator animation) {
if (!show) view.setVisibility(View.INVISIBLE);
}
}
public static void regularFadeView(boolean show, View view) {
view.animate()
.setInterpolator(mDecelerateInterpolator)
.alpha(show ? 1 : 0)
.setListener(getAnimationListener(show, view))
.start();
}
And then on your test:
private void shouldShowViewWhenShowIsTrue() {
View mockedView = Mockito.mock(View.class);
SimpleAnimatorListener animationListener = getAnimationListener(true, mockedView);
animationListener.onAnimationStart(null);
Mockito.verify(mockedView).setVisibility(View.VISIBLE);
}
Even better could be to have instead of a method like getAnimationListener(), would be to create a FadeAnimationListener that would extend SimpleAnimatorListener, and put the animation logic there.
Hope this helps!
Upvotes: 6