August 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-838) Allow Arquillian Drone to handle Robotium

by Karel Piwko (JIRA)

Karel Piwko created ARQ-838: ------------------------------- Summary: Allow Arquillian Drone to handle Robotium Key: ARQ-838 URL: https://issues.jboss.org/browse/ARQ-838 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.next Reporter: Karel Piwko Assignee: Aleksey Shilin Robotium is a Java based framework for testing Android applications using a high level API. Once the integration with Android integration tests is done, it would be convenient to have its support in Arquillian Drone. The key here is to grab current activity from Android context and provide a Solo object which could be injected into test itself. The usage might look similar to the following: {code} @RunWith(Arquillian.class) public class AndroidTest { @Test public void androidActivity(@AndroidActivity HelloAndroid helloAndroid, @Drone Solo solo) { solo.sendKey(Solo.MENU); solo.clickOnText("More"); solo.clickOnText("Preferences"); solo.clickOnText("Edit File Extensions"); Assert.assertTrue(solo.searchText("rtf")); } } {code} Note that the above example does not reflect possible usage of Android/Robotium in class level, this a method-level proposal. -- 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

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] (ARQ-994) Allow Arquillian Drone to wait asynchronously instance creation

by Karel Piwko (JIRA)

Karel Piwko created ARQ-994: ------------------------------- Summary: Allow Arquillian Drone to wait asynchronously instance creation Key: ARQ-994 URL: https://issues.jboss.org/browse/ARQ-994 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.0.0.Final Reporter: Karel Piwko Assignee: Karel Piwko Priority: Critical Drone should create WebDriver/Selenium instances using a Future<> call or similar construction. Sometime, an opening of browser fails (e.g. on Solaris, when something goes wrong, like machine having too many opened files) and create instance never actually returns, causing tests to hang forever.dron -- 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

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-245) When using TestNG, an embedded container (e.g. weld-ee) and multiple test classes, test fail randomly

by Adam Warski (JIRA)

When using TestNG, an embedded container (e.g. weld-ee) and multiple test classes, test fail randomly ----------------------------------------------------------------------------------------------------- Key: ARQ-245 URL: https://jira.jboss.org/browse/ARQ-245 Project: Arquillian Issue Type: Bug Components: Test Harness Integration Affects Versions: 1.0.0.Alpha3 Reporter: Adam Warski As TestNG interleaves tests from different classes (even in single-threaded mode), cleanup of one class (@AfterClass) can happen to be invoked in the middle of executing tests from another class. More precisely, it clears the Container instance: at org.jboss.weld.Container.cleanup(Container.java:108) at org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:460) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockServletLifecycle.endApplication(MockServletLifecycle.java:126) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.stopContainer(TestContainer.java:139) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.undeploy(WeldEEMockContainer.java:131) at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:61) at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:47) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:86) at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:90) at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:227) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:124) at org.testng.TestRunner.runWorkers(TestRunner.java:908) at org.testng.TestRunner.privateRun(TestRunner.java:617) at org.testng.TestRunner.run(TestRunner.java:498) at org.testng.SuiteRunner.runTest(SuiteRunner.java:329) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:324) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:296) at org.testng.SuiteRunner.run(SuiteRunner.java:201) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:915) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:75) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:92) (notice the AfterClass, Arquillian:83), which causes any subsequent test to throw: org.jboss.arquillian.impl.event.FiredEventException: java.lang.IllegalStateException: Singleton is not set at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:113) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:97) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160) at org.testng.internal.Invoker.invokeMethod(Invoker.java:494) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) at org.testng.TestRunner.runWorkers(TestRunner.java:908) at org.testng.TestRunner.privateRun(TestRunner.java:617) at org.testng.TestRunner.run(TestRunner.java:498) at org.testng.SuiteRunner.runTest(SuiteRunner.java:329) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:324) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:296) at org.testng.SuiteRunner.run(SuiteRunner.java:201) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:915) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:75) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:92) Caused by: java.lang.IllegalStateException: Singleton is not set at org.jboss.weld.bootstrap.api.helpers.IsolatedStaticSingletonProvider$IsolatedStaticSingleton.get(IsolatedStaticSingletonProvider.java:52) at org.jboss.weld.Container.instance(Container.java:58) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.getProxiedInstance(ClientProxyMethodHandler.java:138) at org.jboss.weld.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:100) at org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43) at org.jboss.weld.servlet.HttpSessionManager_$$_javassist_14.setSession(HttpSessionManager_$$_javassist_14.java) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer$1.callback(WeldEEMockContainer.java:111) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer$1.callback(WeldEEMockContainer.java:95) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 28 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] (ARQ-872) Integration tests are failing with Glassfish 3.1.2 embedded

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-872: ---------------------------------- Summary: Integration tests are failing with Glassfish 3.1.2 embedded Key: ARQ-872 URL: https://issues.jboss.org/browse/ARQ-872 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha4 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next -- 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

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] (ARQ-763) Create TestNG tests covering most important use cases.

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-763: ---------------------------------- Summary: Create TestNG tests covering most important use cases. Key: ARQ-763 URL: https://issues.jboss.org/browse/ARQ-763 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha3 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next -- 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

13 years, 6 months

1
7
0 / 0

[JBoss JIRA] (ARQ-1017) Update APE to Core 1.0.1.Final

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-1017: ----------------------------------- Summary: Update APE to Core 1.0.1.Final Key: ARQ-1017 URL: https://issues.jboss.org/browse/ARQ-1017 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.next Reporter: Bartosz Majsak Assignee: Bartosz Majsak -- 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

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] (ARQGRA-158) Check and complete all documentation for all features in Alpha2

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-158: --------------------------------- Summary: Check and complete all documentation for all features in Alpha2 Key: ARQGRA-158 URL: https://issues.jboss.org/browse/ARQGRA-158 Project: Arquillian Graphene Issue Type: Task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0.0.Alpha2 -- 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

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (ARQGRA-132) Add BOM usage into documentation

by Karel Piwko (JIRA)

Karel Piwko created ARQGRA-132: ---------------------------------- Summary: Add BOM usage into documentation Key: ARQGRA-132 URL: https://issues.jboss.org/browse/ARQGRA-132 Project: Arquillian Graphene Issue Type: Task Components: doc Reporter: Karel Piwko Assignee: Lukáš Fryč Following documentation at https://docs.jboss.org/author/display/ARQAJO/Getting+Started does not contain anything about dependencyManagement and BOMs which should be there. Usage of BOM should be promoted there. -- 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

13 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQ-579) We need to be able to override default protocol on a container level

by José Freitas (JIRA)

We need to be able to override default protocol on a container level -------------------------------------------------------------------- Key: ARQ-579 URL: https://issues.jboss.org/browse/ARQ-579 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: José Freitas Using <defaultProtocol type="Servlet 3.0" /> makes it impossible to run tests on tomcat-embedded-6. We need to be able to override default protocol on a container level, so we can use defaultProtocol property and still share an arquillian.xml between older servers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
5
0 / 0

[JBoss JIRA] (ARQ-1047) RemoteAddress nor Remote property does not trigger remote webdriver

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1047: -------------------------------- Summary: RemoteAddress nor Remote property does not trigger remote webdriver Key: ARQ-1047 URL: https://issues.jboss.org/browse/ARQ-1047 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Drone Affects Versions: drone_1.1.0.CR2 Reporter: Karel Piwko Assignee: Karel Piwko Priority: Critical Fix For: drone_1.2.0.next When user tries to use Selenium Grid together with Drone, e.g.: {code:java} @Test public void simpleWebdriverTest(@Drone WebDriver webdriver) { webdriver.get(contextPath.toString()); webdriver.findElement(By.id("name")).sendKeys("Samuel"); webdriver.findElement(By.id("email")).sendKeys("samuel(a)vimes.dw"); webdriver.findElement(By.id("phoneNumber")).sendKeys("1234567890"); webdriver.findElement(By.id("register")).submit(); // FIXME with Graphene, you can wait for a request Assert.assertTrue(true); } {code} it is not possible to trigger RemoteWebDriver builder via: -Darquillian.webdriver.remote.address=xyz nor -Darquillian.webdriver.remote=true User can use only RemoteReusable via -Darquillian.webdriver.remote.reusable=true, which is not correct behavior and prevents easy switch between local browser and Selenium Grid. -- 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

13 years, 6 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2012