[JBoss JIRA] (ARQGRA-165) JSInterfaceFactory test case enrichment
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQGRA-165:
---------------------------------
Summary: JSInterfaceFactory test case enrichment
Key: ARQGRA-165
URL: https://issues.jboss.org/browse/ARQGRA-165
Project: Arquillian Graphene
Issue Type: Enhancement
Affects Versions: 2.0.0.Alpha2
Reporter: Lukáš Fryč
Priority: Minor
For creating Java-to-JavaScript calling interface, you need to use call {{JSInterfaceFactory.create(JavaScriptInterfaceToCreate.class)}}.
This is not really handy for direct usage:
{code:java}
@RunWith(Arquillian.class)
public class MyTestCase {
@Drone
private WebDriver browser;
@Test
public void test() throws InterruptedException {
RequestGuard guard = JSInterfaceFactory.create(RequestGuard.class);
Assert.assertEquals(RequestType.HTTP, guard.getRequestDone());
}
{code}
Let's implement test case enrichment, similarly as we did with @FindBy.
You can re-use annotation @JavaScript:
{code:java}
@RunWith(Arquillian.class)
public class MyTestCase {
@Drone
private WebDriver browser;
@JavaScript
RequestGuard guard;
@Test
public void test() throws InterruptedException {
Assert.assertEquals(RequestType.HTTP, guard.getRequestDone());
}
{code}
This injection should work also in component objects.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (ARQGRA-191) Support @Drone and @ArquillianResource in Page objects
by Anthony O. (JIRA)
Anthony O. created ARQGRA-191:
---------------------------------
Summary: Support @Drone and @ArquillianResource in Page objects
Key: ARQGRA-191
URL: https://issues.jboss.org/browse/ARQGRA-191
Project: Arquillian Graphene
Issue Type: Feature Request
Affects Versions: 2.Future
Reporter: Anthony O.
In the same way as ARQGRA-189, I think it could be a good thing to support @Drone in Page objects too.
Here is my use case :
{code}
public class FeatureTest extends Arquillian {
@Page
private HomePage homePage;
@Test
public testClickMenuRedirect() {
FeaturePage featurePage = homePage.open()
.doFeature();
assertEquals(featurePage.getSomeAttributeValue(), "someAttributeValue");
}
}
public class HomePage {
@Drone
private WebDriver driver;
@ArquillianResource
URL contextPath;
@FindBy(id="featureLinkMenu")
private WebElement featureLinkMenu;
public HomePage open() {
driver.get(URLUtils.buildUrl(contextPath, "pages/feature.xhtml");
}
public HomePage doFeature() {
guardHttp(featureLinkMenu).click();
return this;
}
// code for getSomeAttributeValue()
}
{code}
--
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
12 years, 2 months
[JBoss JIRA] (ARQ-1221) Create a managed DeployableContainer integration for WAS Liberty Profile V8.5.Next
by Gerhard Poul (JIRA)
Gerhard Poul created ARQ-1221:
---------------------------------
Summary: Create a managed DeployableContainer integration for WAS Liberty Profile V8.5.Next
Key: ARQ-1221
URL: https://issues.jboss.org/browse/ARQ-1221
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: WebSphere Containers
Reporter: Gerhard Poul
Assignee: Gerhard Poul
Priority: Optional
Create a managed DeployableContainer integration for WebSphere Application Server Liberty Profile V8.5.Next. The Alpha is currently available on wasdev.net.
This implementation should allow complete lifecycle management of the liberty profile as part of the Arquillian test. A test should be implemented testing the ejblite compatibility.
During implementation we should also investigate whether an integration with the new Maven support in liberty profile can be used in combination with Arquillian.
--
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
12 years, 2 months
[JBoss JIRA] (ARQ-1218) Allow spawned processes to log errors
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1218:
--------------------------------
Summary: Allow spawned processes to log errors
Key: ARQ-1218
URL: https://issues.jboss.org/browse/ARQ-1218
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Android
Affects Versions: android_1.0.0.Alpha1
Reporter: Karel Piwko
Assignee: Karel Piwko
Fix For: android_1.0.0.next
Swawned processes ignore error stream by default. Allow error stream and provide a simple way how these errors get to end user.
--
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
12 years, 2 months
[JBoss JIRA] (ARQ-1217) ProcessExecutor might wait infinitely
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1217:
--------------------------------
Summary: ProcessExecutor might wait infinitely
Key: ARQ-1217
URL: https://issues.jboss.org/browse/ARQ-1217
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Android
Reporter: Karel Piwko
Assignee: Karel Piwko
Priority: Blocker
Fix For: android_1.0.0.next
Current process executor, implemented after 1.0.0.Alpha1 release, might lead to infinite waits.
--
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
12 years, 2 months
[JBoss JIRA] (ARQ-1132) If the platform has more than one ABI, the emulator is not created
by Jan Papousek (JIRA)
Jan Papousek created ARQ-1132:
---------------------------------
Summary: If the platform has more than one ABI, the emulator is not created
Key: ARQ-1132
URL: https://issues.jboss.org/browse/ARQ-1132
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Android
Affects Versions: android_1.0.0.Alpha1
Reporter: Jan Papousek
Assignee: Karel Piwko
The creation script looks like:
{code}
${ANDROID_HOME}/tools/android create avd -n <avd name> -t android-<level> -f -p <avd name> -c <sd size>
{code}
If the platform contains more than one ABI, the following error appears:
{code}
Valid ABIs: armeabi-v7a, x86
Error: This platform has more than one ABI. Please specify one using --abi.
{code}
Btw. the eror isn't displayed and is silently ignored by android extension.
Developer should be able to specify ABI or other options in creation script.
--
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
12 years, 2 months