February 2012 - arquillian-issues

[JBoss JIRA] Created: (ARQAJO-88) Add more usage examples to Utility Classes section in docs

by Juraj Huska (JIRA)

Add more usage examples to Utility Classes section in docs ---------------------------------------------------------- Key: ARQAJO-88 URL: https://issues.jboss.org/browse/ARQAJO-88 Project: Arquillian Ajocado Issue Type: Feature Request Components: doc Affects Versions: 1.0.0.CR1 Reporter: Juraj Huska Assignee: Lukáš Fryč The section with Utility Classes should provide code usage examples to show they functionality. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-63) Screencast on Ajocado

by Lukáš Fryč (JIRA)

Screencast on Ajocado --------------------- Key: ARQAJO-63 URL: https://issues.jboss.org/browse/ARQAJO-63 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-64) Blog on Ajocado

by Lukáš Fryč (JIRA)

Blog on Ajocado --------------- Key: ARQAJO-64 URL: https://issues.jboss.org/browse/ARQAJO-64 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQAJO-82) Cross-site request problems for Ajocado

by Karel Piwko (JIRA)

Cross-site request problems for Ajocado --------------------------------------- Key: ARQAJO-82 URL: https://issues.jboss.org/browse/ARQAJO-82 Project: Arquillian Ajocado Issue Type: Feature Request Components: integration Affects Versions: 1.0.0.CR1 Reporter: Karel Piwko Assignee: Lukáš Fryč Evaluate if Ajocado is affected by ARQ-521 and if proprosed solution will work for it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
2
0 / 0

[JBoss JIRA] (ARQAJO-119) isVisible JS condition should not fail when element is not present

by Juraj Huska (JIRA)

Juraj Huska created ARQAJO-119: ---------------------------------- Summary: isVisible JS condition should not fail when element is not present Key: ARQAJO-119 URL: https://issues.jboss.org/browse/ARQAJO-119 Project: Arquillian Ajocado Issue Type: Enhancement Components: api, core Affects Versions: 1.0.0.CR3 Reporter: Juraj Huska Priority: Minor The method isVisible of object selenium is failing (throwing exception element not found), when the element is not present on the page. This behavior is quite unhandy in for invocations such as: {code} waitModel.failWith("Popup did not show").until(elementVisible.locator(popup)); {code} It is only the example, but this will fail and no wait is done at all. To simulate it without failing, one has to write: {code} waitModel.failWith("Popup did not show").until(elementPresent.locator( jq( popup.getRawLocator + ":visible" ) )); {code} So he *has to use elementPresent condition and add :visible locator*, even when he really just wants to verify whether the element is visible, since it is obvious that the element can be present and not be visible at the same time. So my propose will be to *catch* the ElementNotFoundException in selenium invocation of isVisible and to *return false*, when the element is not present. For me this sounds quite reasonably. *Is there any problem with it? Will it be problem to change the Selenium API, and to make it not consistent with standard Selenium 1,2 ?* -- 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
5
0 / 0

[JBoss JIRA] Created: (ARQ-576) The build script bits that downloads and configures 1 or more managed containers should be extracted to a maven plugin, so we don't need to copy paste that logic

by Geoffrey De Smet (JIRA)

The build script bits that downloads and configures 1 or more managed containers should be extracted to a maven plugin, so we don't need to copy paste that logic ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-576 URL: https://issues.jboss.org/browse/ARQ-576 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Maven Plugin Reporter: Geoffrey De Smet Priority: Minor See ARQ-574. Now we have to copy paste something like this, per managed container: {code} <properties> <managed-appserver.download.dir>${project.basedir}/local/managed-appserver</managed-appserver.download.dir> <managed-appserver.tomcat6.version>6.0.33</managed-appserver.tomcat6.version> <managed-appserver.tomcat6.home>${project.build.directory}/apache-tomcat-${managed-appserver.tomcat6.version}</managed-appserver.tomcat6.home> </properties> ... <plugin> <artifactId>maven-antrun-plugin</artifactId> <inherited>false</inherited> <executions> <execution> <phase>generate-test-resources</phase> <configuration> <target> <mkdir dir="${managed-appserver.download.dir}"/> <get src="http://archive.apache.org/dist/tomcat/tomcat-6/v${managed-appserver.tomca..." dest="${managed-appserver.download.dir}" verbose="true" skipexisting="true"/> <unzip src="${managed-appserver.download.dir}/apache-tomcat-${managed-appserver.tomcat6.version}.zip" dest="${project.build.directory}"/> </target> </configuration> <goals> <goal>run</goal> </goals> </execution> </executions> </plugin> <plugin> <artifactId>maven-resources-plugin</artifactId> <executions> <execution> <id>copy-resources</id> <phase>process-test-resources</phase> <goals> <goal>copy-resources</goal> </goals> <configuration> <outputDirectory>${managed-appserver.tomcat6.home}/conf</outputDirectory> <overwrite>true</overwrite> <resources> <resource> <directory>${basedir}/src/test/conf/tomcat6</directory> </resource> </resources> </configuration> </execution> </executions> </plugin> <plugin> <artifactId>maven-surefire-plugin</artifactId> <configuration> <environmentVariables> <CATALINA_HOME>${managed-appserver.tomcat6.home}</CATALINA_HOME> </environmentVariables> </configuration> </plugin> {code} But this changes over time, and since we copy-paste it to our user projects, our copy becomes stale. If this could be extracted somehow (aslak is not in favor of adding this to the managed container runtimes, so probably a maven plugin), that would be nice. Extra optional requirements: - It should be easy to ask for multiple managed appservers (say jboss 7, tomcat 6, jetty 6 and jboss 6) - Prefer zips from the maven repo over "download" url's. At least if the maven repo is down we know that a clean build doesn't work. - What if multiple hudson jobs are testing with arq on the same hudson slave? They can't use the same port! - I prefer downloading to /local instead of /target, because the latter gets deleted during "mvn clean". Then again, if it comes from ~/.m2/repository, neither is needed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
7
0 / 0

[JBoss JIRA] (ARQ-737) Support Byteman Rules in client mode

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-737: --------------------------------- Summary: Support Byteman Rules in client mode Key: ARQ-737 URL: https://issues.jboss.org/browse/ARQ-737 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Byteman Affects Versions: byteman_1.0.0.Alpha1 Reporter: Aslak Knutsen Fix For: byteman_1.0.0.next Byteman needs to attach itself to the Test VM as well as the Server VM. {code} @Test @RunAsClient @BMRule( name = "rule", targetClass = "org.hornetq.core.postoffice.impl.PostOfficeImpl", targetMethod = "processRoute", action = "System.out.println("Hi, it's working.");") public void test() { ... } {code} -- 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
3
0 / 0

[JBoss JIRA] (ARQ-793) Arquillian config-impl-base is not a part of junit|testng-standalone

by Karel Piwko (JIRA)

Karel Piwko created ARQ-793: ------------------------------- Summary: Arquillian config-impl-base is not a part of junit|testng-standalone Key: ARQ-793 URL: https://issues.jboss.org/browse/ARQ-793 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR7 Reporter: Karel Piwko Priority: Critical When configuration was split, the arquillian-config-impl-base was made a dependency of container only {code} ./container/spi/pom.xml: <artifactId>arquillian-config-impl-base</artifactId>  ./container/impl-base/pom.xml: <artifactId>arquillian-config-impl-base</artifactId>  ./bom/pom.xml: <artifactId>arquillian-config-impl-base</artifactId> ./config/impl-base/pom.xml: <artifactId>arquillian-config-impl-base</artifactId> {code} This means that when no container is on classpath, e.g. standalone mode of junit/testng, ArquillianDescriptor is not created at all. -- 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
6
0 / 0

[JBoss JIRA] (ARQ-625) EnterpriseArchive deployment with EJB-JAR without descriptor will fail on WAS V8.0

by Gerhard Poul (Created) (JIRA)

EnterpriseArchive deployment with EJB-JAR without descriptor will fail on WAS V8.0 ---------------------------------------------------------------------------------- Key: ARQ-625 URL: https://issues.jboss.org/browse/ARQ-625 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: WebSphere Containers Environment: WAS V8.0.0.1 Reporter: Gerhard Poul Assignee: Gerhard Poul Priority: Minor A deployment of an EnterpriseArchive that contains an EJB-JAR without a descriptor will fail on WAS V8.0. The errors being logged are from WTP and have message codes of IWAE0006E and IWAE0023E. -- 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

4
3
0 / 0

[JBoss JIRA] Created: (ARQ-337) Create a Context/Scope activation/deactivation abstraction for CDI

by Aslak Knutsen (JIRA)

Create a Context/Scope activation/deactivation abstraction for CDI ------------------------------------------------------------------- Key: ARQ-337 URL: https://jira.jboss.org/browse/ARQ-337 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen We need to have a stable and reliable api exposed by arquillian over the different container types and CDI impls to control the activation and deactivation of different scopes -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2012