July 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-351) @Run(AS_CLIENT) support on lifecycle methods and @Test

by Aslak Knutsen (JIRA)

@Run(AS_CLIENT) support on lifecycle methods and @Test ------------------------------------------------------ Key: ARQ-351 URL: https://issues.jboss.org/browse/ARQ-351 Project: Arquillian Issue Type: Feature Request Components: Base Implementation, Test Harness Integration Reporter: Aslak Knutsen With support for multiple testable deployments and control over lifecycle method execution, we should open for: @Run() on @Test methods, to override a single test method targeted against a testable deployment ot be executed on the client side. @Run() on @BeforeClass/@AfterClass/@Before/@After to support lifecycle methods both on client and incontainer. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-229) Should split API and Impl in two different modules

by Aslak Knutsen (JIRA)

Should split API and Impl in two different modules -------------------------------------------------- Key: ARQ-229 URL: https://jira.jboss.org/browse/ARQ-229 Project: Arquillian Issue Type: Feature Request Components: Extension - Performance Reporter: Aslak Knutsen Assignee: St?le Pedersen Fix For: 1.0.0.Alpha4 ContextAppenders are auto included in the runtime if found on ClassPath. We should consider splitting the performance extension into two modules, api and impl. Where API contains all the user facing annotations etc. With this you can compile against API and only include impl when you actually want to run the test case in performance 'mode', e.g. via a special profile. mvn test -P jbossas-remote-6,performance-test -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-531) Allow Performance extension to measure @Deployment annotated methods

by Karel Piwko (JIRA)

Allow Performance extension to measure @Deployment annotated methods -------------------------------------------------------------------- Key: ARQ-531 URL: https://issues.jboss.org/browse/ARQ-531 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Performance Reporter: Karel Piwko It should be possible to use @Performance on @Deployment methods. This can impose some restrictions on container speed. {code} @Deployment @Performance(relativeTime=10) public static JavaArchive createDeployment() { return ShrinkWrap.create(JavaArchive.class ,"test.jar") .addPackage(WorkHard.class.getPackage()) .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-530) Relative timing for performance timeout

by Karel Piwko (JIRA)

Relative timing for performance timeout --------------------------------------- Key: ARQ-530 URL: https://issues.jboss.org/browse/ARQ-530 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Performance Reporter: Karel Piwko See following idea: Before the test, the extension will benchmark the machine, for example by counting some large loop. Then, instead of ms as in @Performance(time=5), it will be possible to reference time like @Performance(relativeTime=5), meaning that it must be finished sooner that 5 times duration of the loop. This concept can be further extended by configurable relativeUnit, e.g. {code} @PerformanceTest(relativeUnitStrategy=COMPUTED) public TestFoo { @PerformanceTest(relativeTime=5) public void test() { 5x computed loop } } @PerformanceTest(relativeUnitStrategy=DEFINED, relativeUnit=5) public TestFoo2 { @PerformanceTest(relativeTime=5) public void test() { 5x5 } } @PerformanceTest(relativeUnitStrategy=CONFIGURATION) public TestFoo3 { @PerformanceTest(relativeTime=5) public void test() { 5x value in arquillian.xml or in system property } } {code} and finally {code} @PerformanceTest(relativeUnitStrategy=CONFIGURATION) public TestFoo4 { @PerformanceTest(relativeTime=5, time = 50) public void test() { what ever time is shorter will trigger } } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (ARQ-501) Support for 'profiles' inside the Maven Plugin configuration

by Aslak Knutsen (JIRA)

Support for 'profiles' inside the Maven Plugin configuration ------------------------------------------------------------ Key: ARQ-501 URL: https://issues.jboss.org/browse/ARQ-501 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Maven Plugin Reporter: Aslak Knutsen The Maven Plugin should support multiple container sets alla Profiles in regular Maven. e.g. {code} mvn arquillian:deploy -Dqualifier=stage|test {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-315) add configuration property to JBoss AS containers to explode deployment

by Dan Allen (JIRA)

add configuration property to JBoss AS containers to explode deployment ----------------------------------------------------------------------- Key: ARQ-315 URL: https://jira.jboss.org/browse/ARQ-315 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Fix For: 1.0.0.Beta1 In some cases, it's necessary to have JBoss AS explode the deployment on the server. For instance, if the framework (such as Weld Servlet) uses archive scanning, it wouldn't be able to handle the VFS files. While a more formal solution may be appropriate, a stopgap measure is often to have the archive exploded once it arrives at the server. The DeploymentManager offers this option, and thus we should have a configuration property for it. -- 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, 11 months

6
12
0 / 0

[JBoss JIRA] Created: (ARQ-524) Embedded OSGi container cannot find test class

by Thomas Diesler (JIRA)

Embedded OSGi container cannot find test class ---------------------------------------------- Key: ARQ-524 URL: https://issues.jboss.org/browse/ARQ-524 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 1.0.0.Final 14:35:14,390 ERROR [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (main) Failed: org.jboss.test.osgi.example.simple.SimpleBundleTestCase.testBundleInjection: java.lang.ClassNotFoundException: org.jboss.test.osgi.example.simple.SimpleBundleTestCase at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:494) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326) at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231) at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193) at org.jboss.arquillian.osgi.ArquillianBundleActivator$1.loadTestClass(ArquillianBundleActivator.java:65) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:148) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodEmbedded(JMXTestRunner.java:117) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-523) Provide example tests depicting using of injectable Infinispan server descriptor

by Martin Gencur (JIRA)

Provide example tests depicting using of injectable Infinispan server descriptor -------------------------------------------------------------------------------- Key: ARQ-523 URL: https://issues.jboss.org/browse/ARQ-523 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Infinispan Containers Reporter: Martin Gencur Assignee: Martin Gencur The examples should depict using of the framework with both standalone Infinispan server and Enterprise Data Grid. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-513) Implement injectable Infinispan server descriptor for querying information about server

by Martin Gencur (JIRA)

Implement injectable Infinispan server descriptor for querying information about server --------------------------------------------------------------------------------------- Key: ARQ-513 URL: https://issues.jboss.org/browse/ARQ-513 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infinispan Containers Reporter: Martin Gencur Assignee: Martin Gencur It should be possible to inject an Infinispan server descriptor through which one can get information about hostnames, port numbers and various statistics around individual caches running in those servers. Example use: @Infinispan(container="container1") InfinispanInfo inf1; ... inf1.getInstalledEndpoints() [hostname+port couples] inf1.getDefaultCacheManager().getStatistics() inf1.getCache("cache_name").getStatistics() inf1.getCache("cache_name").getStatistics(CacheStatistics.EVICTIONS) ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-519) CommonContainerConfiguration for AS7 should contain managementAddress

by Rostislav Svoboda (JIRA)

CommonContainerConfiguration for AS7 should contain managementAddress --------------------------------------------------------------------- Key: ARQ-519 URL: https://issues.jboss.org/browse/ARQ-519 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: jbossas_1.0.0.CR1 Reporter: Rostislav Svoboda CommonContainerConfiguration (org.jboss.as.arquillian.container) should contain managementAddress. File location jboss-as/arquillian/common/src/main/java/org/jboss/as/arquillian/container/CommonContainerConfiguration.java AS7 can be configured to use different IP addresses for management and public interface. This could be problem for testing in remote mode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2011