From issues at jboss.org Mon Jul 11 07:33:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-42) Reduce logging levels In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQGRA-42: --------------------------------- Assignee: (was: Karel Piwko) > Reduce logging levels > --------------------- > > Key: ARQGRA-42 > URL: https://issues.jboss.org/browse/ARQGRA-42 > Project: Arquillian Graphene > Issue Type: Feature Request > Components: junit, testng > Affects Versions: 1.0.0.Alpha2 > Reporter: Karel Piwko > Priority: Optional > Fix For: 2.2-Tracking > > > Ajocado outputs many debug information under INFO logging level. This level should be reduced to debug or even debug/fine. > It makes execution of the test slower and this information is not required until debugging. > It manifest namely with JUnit which redirects test output to console. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:33:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-384) element().is().visible() prematurely exits with exception on Android In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQGRA-384: ---------------------------------- Assignee: (was: Karel Piwko) > element().is().visible() prematurely exits with exception on Android > -------------------------------------------------------------------- > > Key: ARQGRA-384 > URL: https://issues.jboss.org/browse/ARQGRA-384 > Project: Arquillian Graphene > Issue Type: Bug > Components: core > Affects Versions: 2.0.0.CR1 > Reporter: Karel Piwko > Fix For: 2.0-Tracking > > > When using following call using Graphene and AndroidDriver, it often fails with an exception on Android: > {code} > waitGui().withMessage("Add member button is not yet present.").until().element(addMemberBtn).is().visible(); > {code} > {code} > addUser(com.acme.example.test.DroneTest) Time elapsed: 8.491 sec <<< ERROR! > org.openqa.selenium.WebDriverException: Returned value cannot be converted to Boolean: [org.openqa.selenium.remote.RemoteWebElement at 30 -> unknown locator] > Build info: version: '2.35.0', revision: '8df0c6bedf70ff9f22c647788f9fe9c8d22210e2', time: '2013-08-17 12:46:41' > System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-358.18.1.el6.x86_64', java.version: '1.7.0_25' > Driver info: driver.version: unknown > at org.openqa.selenium.remote.RemoteWebElement.isDisplayed(RemoteWebElement.java:323) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:130) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at com.sun.proxy.$Proxy37.isDisplayed(Unknown Source) > at org.openqa.selenium.support.ui.ExpectedConditions.elementIfVisible(ExpectedConditions.java:228) > at org.openqa.selenium.support.ui.ExpectedConditions.access$100(ExpectedConditions.java:39) > at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:213) > at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:210) > at org.jboss.arquillian.graphene.condition.BooleanConditionWrapper.apply(BooleanConditionWrapper.java:61) > at org.jboss.arquillian.graphene.condition.BooleanConditionWrapper.apply(BooleanConditionWrapper.java:37) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:102) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.commit(WebDriverWaitImpl.java:110) > at org.jboss.arquillian.graphene.wait.IsNotElementBuilderImpl.visible(IsNotElementBuilderImpl.java:57) > at com.acme.example.test.AddMemberPage.addNewMember(AddMemberPage.java:38) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:130) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at com.acme.example.test.AddMemberPage$$EnhancerByGraphene$$75cffd91.addNewMember() > at com.acme.example.test.DroneTest.addUser(DroneTest.java:25) > {code} > This looks like that visibility checker should ignore this exception, as element is in intermediate state at this moment. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:34:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:34:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1129) Investigate poor performance of JGit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-1129 stopped by Karel Piwko. ---------------------------------------- > Investigate poor performance of JGit > ------------------------------------ > > Key: ARQ-1129 > URL: https://issues.jboss.org/browse/ARQ-1129 > Project: Arquillian > Issue Type: Task > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: openshift_1.0.0.next > > > Git operations take too much time. Investigate why. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:34:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:34:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1129) Investigate poor performance of JGit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-1129: -------------------------------- Assignee: (was: Karel Piwko) > Investigate poor performance of JGit > ------------------------------------ > > Key: ARQ-1129 > URL: https://issues.jboss.org/browse/ARQ-1129 > Project: Arquillian > Issue Type: Task > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Karel Piwko > Priority: Critical > Fix For: openshift_1.0.0.next > > > Git operations take too much time. Investigate why. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:34:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:34:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-922) Delete temporary git repository on exit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-922: ------------------------------- Assignee: (was: Karel Piwko) > Delete temporary git repository on exit > --------------------------------------- > > Key: ARQ-922 > URL: https://issues.jboss.org/browse/ARQ-922 > Project: Arquillian > Issue Type: Bug > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Dan Allen > Priority: Minor > > The temporary git repository is not being cleaned up properly on exit. The directory is marked to be deleted on exit of the VM, but for some reason it isn't working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:34:01 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:34:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-911) Report better error if ssh key is not registered with OpenShift account In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-911: ------------------------------- Assignee: (was: Karel Piwko) > Report better error if ssh key is not registered with OpenShift account > ----------------------------------------------------------------------- > > Key: ARQ-911 > URL: https://issues.jboss.org/browse/ARQ-911 > Project: Arquillian > Issue Type: Enhancement > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Dan Allen > Priority: Critical > > The OpenShift container clones the remote git repository configured in arquillian.xml into a temporary directory to exchange files with the test application. The clone is performed over an SSH connection that's negotiated using a public/private RSA key pair. If the public key is not registered with the account, the test fails with the following exception: > {quote} > Exception caught during execution of fetch command > TransportException session is down > {quote} > This sends the developer on a wild goose chase because this error is reported for just about any kind of SSH connection failure. > The problem is revealed if you attempt to ssh into the account: > {quote} > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > {quote} > It would be nice if we could find a way to get this message to be passed through. However, it might be even more useful if we recognize that the connection failure is mostly likely the result of the key not being registered and we can advice the developer > a) how to register it (the client tool command) > b) how to check it > {code} > rhc sshkey add -k ~/.ssh/libra_id_rsa.pub -i libra > ssh -i ~/.ssh/libra_id_rsa 123456789123456789 at TEST_APP-USER_DOMAIN.rhcloud.com > {code} > The full stack trace of the exception is below: > {code} > org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of fetch command > at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:138) > at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:175) > at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:121) > at org.jboss.arquillian.container.openshift.express.OpenShiftRepository.initialize(OpenShiftRepository.java:235) > at org.jboss.arquillian.container.openshift.express.OpenShiftRepository.(OpenShiftRepository.java:75) > at org.jboss.arquillian.container.openshift.express.OpenShiftExpressContainer.start(OpenShiftExpressContainer.java:102) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:198) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > 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.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > 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:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: org.eclipse.jgit.errors.TransportException: ssh://123456789123456789 at TEST_APP-USER_DOMAIN.rhcloud.com/~/git/TEST_APP.git/: session is down > at org.eclipse.jgit.transport.JschSession$JschProcess.(JschSession.java:154) > at org.eclipse.jgit.transport.JschSession$JschProcess.(JschSession.java:118) > at org.eclipse.jgit.transport.JschSession.exec(JschSession.java:91) > at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.(TransportGitSsh.java:248) > at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) > at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:127) > at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:113) > at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1062) > at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:129) > ... 72 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Session.openChannel(Session.java:762) > at org.eclipse.jgit.transport.JschSession$JschProcess.(JschSession.java:147) > ... 80 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:35:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-874) Rename OpenShift Express container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko reassigned ARQ-874: ------------------------------- Assignee: (was: Karel Piwko) > Rename OpenShift Express container > ---------------------------------- > > Key: ARQ-874 > URL: https://issues.jboss.org/browse/ARQ-874 > Project: Arquillian > Issue Type: Feature Request > Components: OpenShift Containers > Affects Versions: openshift_1.0.0.Beta1 > Reporter: Aslak Knutsen > Fix For: openshift_1.0.0.next > > > OpenShift "Express" is no longer used as a term and there will never be a Flex version etc.. > The "OpenShift Express" container should be renamed "OpenShift". Since this currently is in Beta, we should add a maven redirect artifact from "OpenShift Express" to "OpenShift" -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:38:01 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:38:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1783) Update Arquillian Core to 1.1.4.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1783. ---------------------------- > Update Arquillian Core to 1.1.4.Final > ------------------------------------- > > Key: ARQ-1783 > URL: https://issues.jboss.org/browse/ARQ-1783 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.1.Final > > > Update to latest available Core. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:38:02 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:38:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1970) ExecutionException does not escape output from commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1970. ---------------------------- > ExecutionException does not escape output from commands > ------------------------------------------------------- > > Key: ARQ-1970 > URL: https://issues.jboss.org/browse/ARQ-1970 > Project: Arquillian > Issue Type: Bug > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha8 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha9 > > > ExecutionException is using MessageFormat to provide a nice way how to define messages. > However, output of message is not escaped, which means that any string containing *{* will cause exception construction to fail, hiding real problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:38:01 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:38:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1784) Remove obsolote documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1784. ---------------------------- > Remove obsolote documentation > ----------------------------- > > Key: ARQ-1784 > URL: https://issues.jboss.org/browse/ARQ-1784 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.3.1.Final > > > Drone contains references to Graphene 1 and Ajocado, that are no longer valid. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:38:02 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:38:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1469) Improve logging for AbstractWebDriverFactory In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1469. ---------------------------- > Improve logging for AbstractWebDriverFactory > -------------------------------------------- > > Key: ARQ-1469 > URL: https://issues.jboss.org/browse/ARQ-1469 > Project: Arquillian > Issue Type: Bug > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.0.Beta2 > > > Drone currently does not print available implementation classes when FINE level is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:38:02 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:38:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1785) Update Selenium to 2.42.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1785. ---------------------------- > Update Selenium to 2.42.0 > ------------------------- > > Key: ARQ-1785 > URL: https://issues.jboss.org/browse/ARQ-1785 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Drone > Affects Versions: drone_1.3.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.3.1.Final > > > Update to recent Selenium -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:38:02 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:38:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1470) Improve warning message for overriding browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1470. ---------------------------- > Improve warning message for overriding browser > ---------------------------------------------- > > Key: ARQ-1470 > URL: https://issues.jboss.org/browse/ARQ-1470 > Project: Arquillian > Issue Type: Bug > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > Fix For: drone_1.2.0.Beta2 > > > Current message about Arquillian configuration being ignored if "browser" property does not match Java type is confusing. > Configuration is not ignored, it's only browser property which is not honored. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:43:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1657) Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko updated ARQ-1657: ----------------------------- Status: Open (was: Pull Request Sent) > Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment > ----------------------------------------------------------------------- > > Key: ARQ-1657 > URL: https://issues.jboss.org/browse/ARQ-1657 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > > In the past, @OperatesOnDeployment was renamed to @OperateOnDeployment. However, not all occurences of @OperatesOnDeployment were removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jul 11 07:43:00 2016 From: issues at jboss.org (Karel Piwko (JIRA)) Date: Mon, 11 Jul 2016 07:43:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1657) Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karel Piwko closed ARQ-1657. ---------------------------- Resolution: Won't Fix > Inconsistency in usage of @OperateOnDeployment and OperatesOnDeployment > ----------------------------------------------------------------------- > > Key: ARQ-1657 > URL: https://issues.jboss.org/browse/ARQ-1657 > Project: Arquillian > Issue Type: Enhancement > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Minor > > In the past, @OperatesOnDeployment was renamed to @OperateOnDeployment. However, not all occurences of @OperatesOnDeployment were removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jul 20 06:02:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 20 Jul 2016 06:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-2034: ----------------------------------- Assignee: Matous Jobanek > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Bj?rn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jul 20 08:52:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 20 Jul 2016 08:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268096#comment-13268096 ] Matous Jobanek commented on ARQ-2034: ------------------------------------- Hi, good catch. Here is the fix https://github.com/arquillian/arquillian-core/pull/110 Regarding the second suggestion - I can see your point, but AFAIK this is the first event where I can get a reference to a test instance. There is maybe one possibility, I'll try my best a I'll let you know if I find any feasible solution. > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Bj?rn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jul 20 08:52:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 20 Jul 2016 08:52:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2034: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-core/pull/110 > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Bj?rn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jul 22 09:39:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 22 Jul 2016 09:39:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2037) Support additional browser capabilities for Chrome In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2037: ----------------------------------- Summary: Support additional browser capabilities for Chrome Key: ARQ-2037 URL: https://issues.jboss.org/browse/ARQ-2037 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Affects Versions: drone_2.0.0.Final Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.1.0.Final Support additional browser capabilities for Chrome & remove obsolete solution that uses chrome.switches https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/ChromeDriverFactory.java#L86 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jul 26 10:22:00 2016 From: issues at jboss.org (vinoth selvaraj (JIRA)) Date: Tue, 26 Jul 2016 10:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2038) Create Drone extension for Appium In-Reply-To: References: Message-ID: vinoth selvaraj created ARQ-2038: ------------------------------------ Summary: Create Drone extension for Appium Key: ARQ-2038 URL: https://issues.jboss.org/browse/ARQ-2038 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Reporter: vinoth selvaraj Appium is becoming an industry standard for mobile testing. Many large companies like Amazon, Zameron, Perfecto Mobile and others decided to put Appium into their clouds. Appium supports both andriod and ios automation. It would be nice to have a drone-extension for Appium. More Info on appium: *https://github.com/appium/appium* -- This message was sent by Atlassian JIRA (v6.4.11#64026)