February 2012 - arquillian-issues

[JBoss JIRA] (ARQAJO-101) Using of JQuery 1.5 causes that JQuery selectors are not escaped properly

by Juraj Huska (Created) (JIRA)

Using of JQuery 1.5 causes that JQuery selectors are not escaped properly ------------------------------------------------------------------------- Key: ARQAJO-101 URL: https://issues.jboss.org/browse/ARQAJO-101 Project: Arquillian Ajocado Issue Type: Bug Components: core Affects Versions: 1.0.0.CR2 Environment: Ajocado 1.0.0-SNAPSHOT Reporter: Juraj Huska Assignee: Lukáš Fryč When I want to use JQuery selectors in my tests, I can not just type: {code} jq("input[id$=attributes:handleClassInput]"); {code} since it will not be properly escaped, and thus will fail to create this JQuery Locator. I can avoid it by escaping it manually, but it will too much work for my big test suite, which already worked with RichFaces Selenium properly. The reason why *it works in RichFaces Selenium is that it uses JQuery v1.4.4 and Ajocado is using 1.5.* With 1.4.4 it works fine also in Ajocado. -- 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, 7 months

8
14
0 / 0

[JBoss JIRA] (ARQAJO-111) Support Thread-Local Context with Selenium 2

by Lukáš Fryč (Created) (JIRA)

Support Thread-Local Context with Selenium 2 -------------------------------------------- Key: ARQAJO-111 URL: https://issues.jboss.org/browse/ARQAJO-111 Project: Arquillian Ajocado Issue Type: Feature Request Components: core Reporter: Lukáš Fryč Fix For: 2.0-Tracking -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-520) ResolutionException for artifact org.jboss.arquillian.osgi:arquillian-osgi-bundle:jar

by Thomas Diesler (JIRA)

ResolutionException for artifact org.jboss.arquillian.osgi:arquillian-osgi-bundle:jar ------------------------------------------------------------------------------------- Key: ARQ-520 URL: https://issues.jboss.org/browse/ARQ-520 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Affects Versions: osgi_1.0.0.CR2 Reporter: Thomas Diesler Assignee: Thomas Diesler When the JBoss Nexus repo is not defined in ~/.m2/settings.xml we get org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to resolve an artifact at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:324) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:70) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl$MavenArtifactBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:471) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl$MavenArtifactBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:405) at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.installBundle(EmbeddedDeployableContainer.java:182) at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.start(EmbeddedDeployableContainer.java:108) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
6
0 / 0

[JBoss JIRA] Created: (ARQ-338) All test case to specify a list of support bundles

by Thomas Diesler (JIRA)

All test case to specify a list of support bundles -------------------------------------------------- Key: ARQ-338 URL: https://jira.jboss.org/browse/ARQ-338 Project: Arquillian Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler ARQ OSGi tests may have the need to install the arquillian-osgi-bundle before they can run -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-301) Create a Spring framework integration (for non-standalone containers)

by Dan Allen (JIRA)

Create a Spring framework integration (for non-standalone containers) --------------------------------------------------------------------- Key: ARQ-301 URL: https://jira.jboss.org/browse/ARQ-301 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Implement a Spring framework integration. We want to be able to execute Spring tests in non-standalone containers (e.g., Java EE, Servlet). These containers don't have the Spring framework programming model out of the box. So we need to ship it to the server along with the test. That's the purpose of an Arquillian framework integration, so it's an ideal solution. -- 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

12 years, 7 months

4
12
0 / 0

[JBoss JIRA] Created: (ARQ-454) Console log output in Arquillian and JBoss Container Managed 6

by Ove Ranheim (JIRA)

Console log output in Arquillian and JBoss Container Managed 6 -------------------------------------------------------------- Key: ARQ-454 URL: https://issues.jboss.org/browse/ARQ-454 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: JBoss Containers Affects Versions: 1.0.0.Alpha5 Reporter: Ove Ranheim It should be possible to configure console log output in in arquillian.xml, so the logger would redirected server.log to console output. This would require a change in ServiceController: http://anonsvn.jboss.org/repos/jbossas/projects/server-manager/tags/1.0.4... For Bamboo users; Bamboo Jobs are sniffing on the console log output and is sensitive about that, so to get proper integration tests running, this is a requirement. This issue should probably be raised with Ryan Campbell. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-583) When missing a vital part of an ARQ test a meaningful exception should be thrown

by Jason Porter (JIRA)

When missing a vital part of an ARQ test a meaningful exception should be thrown -------------------------------------------------------------------------------- Key: ARQ-583 URL: https://issues.jboss.org/browse/ARQ-583 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR4 Reporter: Jason Porter For example if you're missing a @Deployment, an error stating as much should be thrown. There may be some others, but this one comes to the top. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] (ARQ-697) Exception "Could not deploy to container" should report the real exception why the managed server is failing

by Geoffrey De Smet (Created) (JIRA)

Exception "Could not deploy to container" should report the real exception why the managed server is failing ------------------------------------------------------------------------------------------------------------ Key: ARQ-697 URL: https://issues.jboss.org/browse/ARQ-697 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Critical Currently, when something goes wrong in a managed server, such as ARQ-660, you get a meaningless exception "Could not deploy to container". The real exception should be reported, for example "port in use". It's furthermore unclear, how far this "Could not deploy to container" stretches: if we have a bug in our CDI configuration (such as an Ambiguous dependency) in our war, will it also be reported as such or not? -- 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, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (ARQ-585) Support for adding a beans.xml without discarding the original beans.xml with .mergeAsResource()

by Geoffrey De Smet (JIRA)

Support for adding a beans.xml without discarding the original beans.xml with .mergeAsResource() ------------------------------------------------------------------------------------------------ Key: ARQ-585 URL: https://issues.jboss.org/browse/ARQ-585 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Critical Presume these 2 beans.xml files: Production code: beans.xml: {code} <beans xmlns="http://java.sun.com/xml/ns/javaee" ...>  </beans> {code} Test addition: test-beans.xml: {code} <beans xmlns="http://java.sun.com/xml/ns/javaee" ...> <alternatives> <class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class> </alternatives> </beans> {code} Now, for non-test runs (such as in the IDE or in production), only the beans.xml is activated through weld and the test-only alternative should not be activated. For test runs, the test-only alternative should be activated, yet the rest of the content from beans.xml should be in there too. So it should be merged to something like this: {code} <beans xmlns="http://java.sun.com/xml/ns/javaee" ...>  <alternatives> <class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class> </alternatives> </beans> {code} It would be nice if we do something like mergeAsResource(), shown in this example: {code} public static WebArchive createDeployment() { WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class, "guvnor-webapp-5.3.0-SNAPSHOT.war") .importDirectory(new File("target/guvnor-webapp-5.3.0-SNAPSHOT/")) .as(WebArchive.class) .mergeAsResource(new File("target/test-classes/META-INF/test-beans.xml"), "META-INF/beans.xml") .addAsResource(new File("target/test-classes/"), ArchivePaths.create("")) .addAsLibraries( DependencyResolvers.use(MavenDependencyResolver.class) .includeDependenciesFromPom("pom.xml") .resolveAsFiles(new ScopeFilter("test"))); return webArchive; } {code} Because of maintenance, copying everything from beans.xml to test-beans.xml on every change to beans.xml is NOT an option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
14
0 / 0

[JBoss JIRA] Created: (ARQ-615) Arquillian must scale to a high number of full-layer integration tests

by Geoffrey De Smet (JIRA)

Arquillian must scale to a high number of full-layer integration tests ---------------------------------------------------------------------- Key: ARQ-615 URL: https://issues.jboss.org/browse/ARQ-615 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Critical A full-layer integration test is an arquillian test which deploys the entire war of a webapp (for example guvnor-webapp) and then runs a higher number of test classes and test methods on it. Currently arquillian doesn't scale out to that. For different reasons. The main reason is ARQ-197: every test case starts the container again and after a while tomcat6-managed goes out of memory. But there are other reasons. This should be tested. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2012