[arquillian-issues] [JBoss JIRA] (ARQ-1536) Provide @StartActivity annotation put on test method to automatically start activity
Stefan Miklosovic created ARQ-1536:
--------------------------------------
Summary: Provide @StartActivity annotation put on test method to
automatically start activity
Key: ARQ-1536
URL: https://issues.jboss.org/browse/ARQ-1536
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha2
Reporter: Stefan Miklosovic
Instead of starting activity every time in test method manually, it would be nice to have
this possibility:
{code}
@Test
@InSequence(4)
@OperateOnDeployment("todo-mobile-app")
public void loginUserInMobile(@ArquillianResource AndroidDevice device) {
device.getActivityManagerProvider()
.getActivityManager()
.startActivity("org.jboss.aerogear.todo.activities.LoginActivity");
loginMobileFragment.login("john", "123");
}
=========================
@Test
@InSequence(4)
@OperateOnDeployment("todo-mobile-app")
@StartActivity("org.jboss.aerogear.todo.activities.LoginActivity")
public void loginUserInMobile() {
loginMobileFragment.login("john", "123");
}
{code}
However, with the possibility to have Graphene page fragments, it would be teoretically
possible to have propper page objects as well which mean that we could abstract activity
into @Page and specify its @Location("activityName")
The problem is, how this translates to Graphene since Droidium starts activities in this
manner:
driver.get("and-activity://" + activityName);
There is the need to take that "and-activity" string into consideration with
@Location annotation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira