tree 8c70ad1eaeabdc1447370ef45b1102a1239a189d
parent fe3703b6ac1433e3f8d1cf10a9b37242b68b2845
author Jeremy Woods <jbwoods@google.com> 1564688401 -0700
committer Jeremy Woods <jbwoods@google.com> 1564692878 -0700

Fix saveWhileAnimatingAway() local test failures

FragmentAnimatorTest saveWhileAnimatingAway() test can fail locally
because of animations ending before asserts can be reached.

We should not wait 2 cycles after executing pending transactions on the
FragmentManager. Executing pending transactions forces the animation to
begin and by waiting 2 cycles, it is given a chance to end. Instead,
after we executing pending transactions, we should ensure animations
have been started, then do our asserts. This ensures that even if the
animations were to run with a duration of 0, we still would do our
asserts before the fragment gets marked as inactive. So we should no
longer have to rely on timing for this test to be successful.

Test: all tests pass
FIXES: 138798649
Change-Id: I43f44c535f02ca8af19dce5c787542a7a22f6284