May 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQAJO-65) Expose new interface providing access to initialization and finalization of Ajocado

by Lukáš Fryč (JIRA)

Expose new interface providing access to initialization and finalization of Ajocado ----------------------------------------------------------------------------------- Key: ARQAJO-65 URL: https://issues.jboss.org/browse/ARQAJO-65 Project: Arquillian Ajocado Issue Type: Task Components: api Affects Versions: 1.0.0.Alpha2 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Alpha3 We will need to expose functionality around initialization. This can be satisfied by providing Implementation specific interface for all following tasks: * initializeBrowser * initializeSeleniumExtensions * initializePageExtensions * configureBrowser * finalizeBrowser Using these methods, we can also expose new feature to user, which will satisfy restart of browser (for ensuring clean browser session), this should be placed directly in AjaxSelenium interface. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQAJO-56) Discontinue functionality in TestNG module, delegating to Arquillian Drone

by Lukáš Fryč (JIRA)

Discontinue functionality in TestNG module, delegating to Arquillian Drone -------------------------------------------------------------------------- Key: ARQAJO-56 URL: https://issues.jboss.org/browse/ARQAJO-56 Project: Arquillian Ajocado Issue Type: Task Components: testng Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Alpha3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQAJO-59) Create Drone JIRAs for all features which will be missing when discontinuing TestNG module

by Lukáš Fryč (JIRA)

Create Drone JIRAs for all features which will be missing when discontinuing TestNG module ------------------------------------------------------------------------------------------ Key: ARQAJO-59 URL: https://issues.jboss.org/browse/ARQAJO-59 Project: Arquillian Ajocado Issue Type: Sub-task Reporter: Lukáš Fryč Assignee: Lukáš Fryč -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQAJO-43) Configure RF tests for using AjocadoRunner to verify it's functionality

by Lukas Fryc (JIRA)

Configure RF tests for using AjocadoRunner to verify it's functionality ----------------------------------------------------------------------- Key: ARQAJO-43 URL: https://issues.jboss.org/browse/ARQAJO-43 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 1.0.0.Alpha3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-265) Support injection of MC Beans in JBoss AS Containers

by Aslak Knutsen (JIRA)

Support injection of MC Beans in JBoss AS Containers ---------------------------------------------------- Key: ARQ-265 URL: https://jira.jboss.org/browse/ARQ-265 Project: Arquillian Issue Type: Feature Request Components: Jetty Containers Reporter: Aslak Knutsen Support use of @Inject from MC in TestCases Lookup Kernel and resolve beans, or install test case as a MCBean ? -- 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

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-247) Using the tomcat 6 embedded profile, @AfterClass methods are called after each test and method dependencies don't work

by Adam Warski (JIRA)

Using the tomcat 6 embedded profile, @AfterClass methods are called after each test and method dependencies don't work ---------------------------------------------------------------------------------------------------------------------- Key: ARQ-247 URL: https://jira.jboss.org/browse/ARQ-247 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Affects Versions: 1.0.0.Alpha3 Reporter: Adam Warski If there are dependent tests (@Test(dependsOnMethods = "...")), TestNG throws this exception: org.testng.TestNGException: TestClass.testBBB() is not allowed to depend on public void TestClass.testAAA() throws java.lang.Exception at org.testng.internal.MethodHelper.findMethodsNamed(MethodHelper.java:149) Moreover, @AfterClass methods are called after each test, and additionally after the whole class. Same with @BeforeClass. -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-439) CDI in Tomcat Remote Container doesn't work

by Ondrej Zizka (JIRA)

CDI in Tomcat Remote Container doesn't work ------------------------------------------- Key: ARQ-439 URL: https://issues.jboss.org/browse/ARQ-439 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: 1.0.0.Alpha5 Environment: Tomcat 6.0.32 (JBoss EWS 1.0.2.CR2) Reporter: Ondrej Zizka See the testcase org.jboss.arquillian.container.tomcat.remote_6.TomcatRemoteInContainerTestCase in https://github.com/arquillian/arquillian-container-tomcat/pull/1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (ARQ-262) Add a Tomcat remote container

by Pete Muir (JIRA)

Add a Tomcat remote container ----------------------------- Key: ARQ-262 URL: https://jira.jboss.org/browse/ARQ-262 Project: Arquillian Issue Type: Feature Request Components: Tomcat Containers Affects Versions: 1.0.0.Alpha3 Reporter: Pete Muir -- 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

14 years, 9 months

3
13
0 / 0

[JBoss JIRA] Created: (ARQ-238) Create a DeployableContainer integration for JBoss AS 4.2

by Aslak Knutsen (JIRA)

Create a DeployableContainer integration for JBoss AS 4.2 --------------------------------------------------------- Key: ARQ-238 URL: https://jira.jboss.org/browse/ARQ-238 Project: Arquillian Issue Type: Feature Request Components: Documentation, JBoss Containers Reporter: Aslak Knutsen Create a implementation that can talk to JBoss AS 4.2.x -- 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

14 years, 9 months

4
17
0 / 0

[JBoss JIRA] Created: (ARQ-365) Clear up use of ProfileName, not the same as ProfileKey in ProfileService

by Aslak Knutsen (JIRA)

Clear up use of ProfileName, not the same as ProfileKey in ProfileService ------------------------------------------------------------------------- Key: ARQ-365 URL: https://issues.jboss.org/browse/ARQ-365 Project: Arquillian Issue Type: Bug Components: Documentation, JBoss Containers Affects Versions: 1.0.0.Alpha4 Reporter: Aslak Knutsen profileName is used in Managed and Embedded to specify which server profile (directory) to use; "default", "standard", "all", etc Later the same value is used to load the ProfileService profile. profileName is used with Remote to specify which ProfileService profile to load. This is wrong. The ProfileService Profile is either "deployments", "deployers" or "farm", referring to the directory within the server profile(+ how to install them in MC). >From Arquillians point of view, the ProfileService Profile should always be "deployments", and the profileName configuration option can be removed from the Remote containers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2011