[JBoss JIRA] (ARQ-1110) can't create IPhoneDriver
by Jan Papousek (JIRA)
Jan Papousek created ARQ-1110:
---------------------------------
Summary: can't create IPhoneDriver
Key: ARQ-1110
URL: https://issues.jboss.org/browse/ARQ-1110
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: 1.0.2.Final
Reporter: Jan Papousek
Assignee: Jan Papousek
IPhoneDriverFactory tries to create an IPhoneDriver with the given remote address and capabilities, but IPhoneDriver doesn't this type of constructor.
{code}
java.lang.IllegalStateException: Unable to find a constructor for implementation class org.openqa.selenium.iphone.IPhoneDriver(URL,DesiredCapabilities). Please make sure that you haven't misconfigured Arquillian Drone, e.g. you set an implementationClass which does not match the field/parameter type in your code.
at org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance(SecurityActions.java:144)
at org.jboss.arquillian.drone.webdriver.factory.IPhoneDriverFactory.createInstance(IPhoneDriverFactory.java:84)
at org.jboss.arquillian.graphene.drone.factory.GrapheneIPhoneDriverFactory.createInstance(GrapheneIPhoneDriverFactory.java:74)
at org.jboss.arquillian.graphene.drone.factory.GrapheneIPhoneDriverFactory.createInstance(GrapheneIPhoneDriverFactory.java:39)
at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129)
at org.jboss.arquillian.graphene.drone.factory.GrapheneWebDriverFactory.createInstance(GrapheneWebDriverFactory.java:80)
at org.jboss.arquillian.graphene.drone.factory.GrapheneWebDriverFactory.createInstance(GrapheneWebDriverFactory.java:41)
at org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.drone.impl.DroneConfigurator.configureDrone(DroneConfigurator.java:116)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
at org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:103)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:77)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:110)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:106)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:113)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
{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
13 years, 5 months
[JBoss JIRA] (ARQ-1165) Remove ChromeDriver tests exclusions
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1165:
--------------------------------
Summary: Remove ChromeDriver tests exclusions
Key: ARQ-1165
URL: https://issues.jboss.org/browse/ARQ-1165
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_1.1.0.CR3
Reporter: Karel Piwko
Assignee: Karel Piwko
Priority: Minor
Fix For: drone_1.1.0.Final
It is no longer necessary to exclude ChromeDriver tests from default test run.
--
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
13 years, 5 months
[JBoss JIRA] (ARQ-1170) Update Selenium to 2.25.0
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1170:
--------------------------------
Summary: Update Selenium to 2.25.0
Key: ARQ-1170
URL: https://issues.jboss.org/browse/ARQ-1170
Project: Arquillian
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_1.1.0.CR3
Reporter: Karel Piwko
Assignee: Karel Piwko
Fix For: drone_1.1.0.Final
Update Selenium to latest available, which is 2.25.0.
--
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
13 years, 5 months
[JBoss JIRA] (ARQ-1173) Remove the javaHome configuration property for the WLS containers
by Vineet Reynolds (JIRA)
Vineet Reynolds created ARQ-1173:
------------------------------------
Summary: Remove the javaHome configuration property for the WLS containers
Key: ARQ-1173
URL: https://issues.jboss.org/browse/ARQ-1173
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: WebLogic Containers
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Priority: Minor
The javaHome property in the {{CommonWebLogicConfiguration}} class is and never was utilized by the container. Remove the property to avoid confusing users of it's purpose.
--
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
13 years, 5 months
[JBoss JIRA] (ARQ-1166) Check if current deployment is same as from metadata
by Bernard Labno (JIRA)
Bernard Labno created ARQ-1166:
----------------------------------
Summary: Check if current deployment is same as from metadata
Key: ARQ-1166
URL: https://issues.jboss.org/browse/ARQ-1166
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - JRebel
Reporter: Bernard Labno
Assignee: Bernard Labno
[10:09] <aslak> one example from the JavaOne demo: I had ran the example with jrebel earlier and it worked during preparation.
[10:10] <aslak> but not during the demo, because at demo time i had disabled the extension and ran a few other tests, then enabled it again. strange exceptions started to happen
[10:10] == mnovak [mnovak@nat/redhat/x-vnphfxzlziqohqfq] has joined #jbosstesting
[10:10] <aslak> the reason was that i hadn't cleaned up target, so the extension falsely found the old deployment metadata and assumed it was deployed
[10:11] <blabno> aslak: that's what i suspected
[10:11] == chm007 [~cmoulliar(a)ip-83-134-24-63.dsl.scarlet.be] has joined #jbosstesting
[10:11] <blabno> aslak: devs need to remember to cleanup target
[10:12] <aslak> just wondering if there is some kind of check we can do to know if we're running within the same 'run' or not
[10:12] <aslak> basically knowing if what we assume is deployed is actually deployed.
[10:13] <aslak> pr spi now, we can't check if a deployment is deployed
[10:13] <aslak> but can we detect this in some other way
[10:15] <blabno> aslak: we could add servlet that would return deployments checksum
[10:15] <blabno> same as in metadata
[10:15] <aslak> hmm.. that's an option
[10:16] <aslak> we have the ProtocolMetadata stored, so we know the details of where that should be deployed
[10:16] <aslak> ip/port/context
--
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
13 years, 5 months