November 2011 - arquillian-issues

[JBoss JIRA] (ARQ-638) Option to "clean" the container before running tests

by Ondrej Zizka (Created) (JIRA)

Option to "clean" the container before running tests ---------------------------------------------------- Key: ARQ-638 URL: https://issues.jboss.org/browse/ARQ-638 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration, JBoss Containers Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka It would be nice to have an option to have the container cleaned before launching it. For AS7 as an example, that would mean deleting * standalone/log * standalone/data * standalone/tmp * standalone/deployments (?) -- 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

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] (ARQ-645) @ArquillianResource @OperatesOnDeployment("foo") URL; for multiple containers

by Marek Schmidt (Created) (JIRA)

@ArquillianResource @OperatesOnDeployment("foo") URL; for multiple containers ----------------------------------------------------------------------------- Key: ARQ-645 URL: https://issues.jboss.org/browse/ARQ-645 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Marek Schmidt It would be nice to support something like @Test @RunAsClient public void test(@ArquillianResource @OperatesOnDeployment("foo") URL foo, @ArquillianResource @OperatesOnDeployment("bar") URL foo) { ... } for functional clustering tests. -- 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

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] Created: (ARQ-561) Make Arquillian compatible with JUnit Parametrized runner

by Ondrej Skutka (JIRA)

Make Arquillian compatible with JUnit Parametrized runner --------------------------------------------------------- Key: ARQ-561 URL: https://issues.jboss.org/browse/ARQ-561 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Test Harness Integration Reporter: Ondrej Skutka Make Arquillian runner compatible with JUnit's Parametrized runner (org.junit.runners.Parameterized). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
10
0 / 0

[JBoss JIRA] (ARQ-636) Add Remote support to the Spock TestRunner

by Aslak Knutsen (Created) (JIRA)

Add Remote support to the Spock TestRunner ------------------------------------------ Key: ARQ-636 URL: https://issues.jboss.org/browse/ARQ-636 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Spock TestRunner Reporter: Aslak Knutsen Fix For: spock_1.0.0.next Spock TestRunner should support running in a Remote Container, e.g. JBoss AS -- 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

14 years, 2 months

4
5
0 / 0

[JBoss JIRA] (ARQ-675) Update Spock Test Runner pom setup to match other extensions, arquillian-bom, jboss-parent, maven-release etc

by Aslak Knutsen (Created) (JIRA)

Update Spock Test Runner pom setup to match other extensions, arquillian-bom, jboss-parent, maven-release etc -------------------------------------------------------------------------------------------------------------- Key: ARQ-675 URL: https://issues.jboss.org/browse/ARQ-675 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Spock TestRunner Reporter: Aslak Knutsen Assignee: Bartosz Majsak Fix For: spock_1.0.0.next -- 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

14 years, 2 months

6
6
0 / 0

[JBoss JIRA] Created: (ARQ-348) Create a Byteman integration

by Aslak Knutsen (JIRA)

Create a Byteman integration ---------------------------- Key: ARQ-348 URL: https://issues.jboss.org/browse/ARQ-348 Project: Arquillian Issue Type: Feature Request Components: Frameworks Reporter: Aslak Knutsen Assignee: Aslak Knutsen http://www.jboss.org/byteman Add support for BMRule(s)/BMScript to be executed against Targeted Deployments. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
5
0 / 0

[JBoss JIRA] (ARQAJO-100) Allow user to fail tests with AssertionError() with wait* objects

by Karel Piwko (Created) (JIRA)

Allow user to fail tests with AssertionError() with wait* objects ----------------------------------------------------------------- Key: ARQAJO-100 URL: https://issues.jboss.org/browse/ARQAJO-100 Project: Arquillian Ajocado Issue Type: Feature Request Components: core Affects Versions: 1.0.0.CR2 Reporter: Karel Piwko Assignee: Lukáš Fryč Expecting user want to fail (e.g. marking as failure instead of error) his test if some element is not present: {code} waitModel.failWith(new AssertionError("Invalid message not present")).until(elementPresent.locator(REG_INVALID)); {code} This is not possible. User has do to it following way. {code} waitModel.dontFail().until(elementPresent.locator(REG_INVALID)); Assert.assertTrue("Invalid message not present", selenium.isElementPresent(REG_INVALID)); {code} This is either an usability problem or a complete misunderstood of the usage by myself. -- 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

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-79) Forge integration

by Lukáš Fryč (JIRA)

Forge integration ----------------- Key: ARQAJO-79 URL: https://issues.jboss.org/browse/ARQAJO-79 Project: Arquillian Ajocado Issue Type: Feature Request Components: planning Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQAJO-89) Thread-Local Contexts section in docs should be more clean even for people not so familiar with given topic

by Juraj Huska (JIRA)

Thread-Local Contexts section in docs should be more clean even for people not so familiar with given topic ----------------------------------------------------------------------------------------------------------- Key: ARQAJO-89 URL: https://issues.jboss.org/browse/ARQAJO-89 Project: Arquillian Ajocado Issue Type: Feature Request Components: doc Affects Versions: 1.0.0.CR1 Reporter: Juraj Huska Assignee: Lukáš Fryč Thread-Local Contexts section in docs should be more clean even for people not so familiar with given topic. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-533) Support Qualifiers on @ArquillianResource in ResourceProvider's SPI

by Aslak Knutsen (JIRA)

Support Qualifiers on @ArquillianResource in ResourceProvider's SPI ------------------------------------------------------------------- Key: ARQ-533 URL: https://issues.jboss.org/browse/ARQ-533 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Reporter: Aslak Knutsen Fix For: 1.1.0.Beta1 ResourceProvider only support the @ArquillianResource annotation, in some cases we need to be able to specify more metadata for a injection point. Following CDI, we can add Qualifier annotations. @ArquillianResource(MyServlet.class) @Container("container-1") private URL url; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2011