Open GoogleCodeExporter opened 9 years ago
Forgot to mention. When I create a non-fullscreen app (using blank template),
performing click works fine. So, the issue is only with fullscreen app.
Original comment by ragunath...@gmail.com
on 29 Mar 2015 at 1:30
Thanks for the detailed bug report. We can investigate further, but my first
reaction to seeing the error is that it might be impossible to do anything in
this case.
Are there specific bugs that you're hoping to catch with full screen mode that
might not show up if you test the activity in normal mode?
Original comment by vale...@google.com
on 30 Mar 2015 at 8:47
The app starts fullscreen. Fullscreen activity code template which provides
this behavior out of the box. In order to come to normal mode, performing
action (say click) is required. So this is catch 22.
Even if the app does not start on fullscreen mode, there are typical scenarios
any app would need to test on fullscreen. For instance, if you take Pocket
(https://play.google.com/store/apps/details?id=com.ideashower.readitlater.pro&hl
=en), scrolling down or swipe up takes the activity to fullscreen; scrolling
up or swipe down or touch brings back the action bar, navigation, etc. Espresso
shall support testing such transitions.
Also, due to additional screen real estate, apps have the option to expose
extra features (say through buttons) which may go away in normal mode. Not sure
if this is standard UX on android, yet given a design like this, espresso would
be expected to help in testing these fullscreen only features.
Original comment by ragunath...@gmail.com
on 30 Mar 2015 at 11:43
Original comment by nkors...@google.com
on 5 May 2015 at 5:41
public class FullscreenActivityTest extends ActivityInstrumentationTestCase2 {
public FullscreenActivityTest() {
super(FullscreenActivity.class);
}
}
Original issue reported on code.google.com by
ragunath...@gmail.com
on 29 Mar 2015 at 1:26Attachments: