Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Espresso does not wait until next activity to be resumed to proceed to next action #55

Open
GoogleCodeExporter opened this issue May 26, 2015 · 17 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. In Espresso, click any view that will launch a new activity, or click back 
to go back to the previous activity
2. At the next line, do check isDisplayed() on any view in the next activity

What is the expected output? What do you see instead?
Expected: The check returned without problem
Actual: Sometimes it performs the check too quick, and the UI is still in the 
current activity. In that case, a NoMatchingViewException is thrown.

What version of the product are you using? On what operating system?
Android emulator 4.1.2

Please provide any additional information below.
This does not happen very often. Maybe just one out of 100 tries. That doesn't 
sound very high if this is an app, but that's very high for Continuous Delivery 
automation. For any test suite that has more than 100 test scripts doing this, 
it's almost guaranteed to fail. For automation in Continuous Delivery, we are 
looking for one out of a million tries stability, and I think that's what 
Espresso is supposed to do.

Original issue reported on code.google.com by [email protected] on 11 Feb 2014 at 7:10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant