April 2010 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-103) Create a JBoss Reloaded Container implementation

by Andrew Lee Rubinger (JIRA)

Create a JBoss Reloaded Container implementation ------------------------------------------------ Key: ARQ-103 URL: https://jira.jboss.org/jira/browse/ARQ-103 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Let's avoid the MCServer, VDF, and VFS APIs in our test harnesses and supply an Arquillian Container to do this for us. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQ-115) Wrong chaining for spi.LifecycleException

by Jesper Pedersen (JIRA)

Wrong chaining for spi.LifecycleException ----------------------------------------- Key: ARQ-115 URL: https://jira.jboss.org/jira/browse/ARQ-115 Project: Arquillian Issue Type: Feature Request Components: Deployable Containers SPI Affects Versions: 1.0.0.Alpha1 Reporter: Jesper Pedersen Priority: Minor The spi.LifecycleException has public LifecycleException(String message, Exception cause) It should be public LifecycleException(String message, Throwable cause) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-126) rename RunModeType.REMOTE to RunModeType.IN_CONTAINER

by Dan Allen (JIRA)

rename RunModeType.REMOTE to RunModeType.IN_CONTAINER ----------------------------------------------------- Key: ARQ-126 URL: https://jira.jboss.org/jira/browse/ARQ-126 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen I think that the combination of the terms LOCAL and REMOTE in the RunModeType enum is confusing. RunModeType is attempting to describe where the test runs in relationship to the test runner. In that case, the terms are defensible. LOCAL = test is local to the test runner (same JVM) REMOTE = test is remote from the test runner (different JVM) In the case of LOCAL, the test must use remote communication to invoke the code under test. This is where we overuse the term "remote". The term "remote" implies remote communication, but it's not clear what is remote from the standpoint of the test writer. We are describing internal behavior. And besides, REMOTE isn't entirely accurate since in embedded containers, no remote communication is used. It's more natural to describe where the test is in relation to the code under test. In that case, local means that the test case stays behind. The other term would be in-container, which may or may not be remote. It's about the packaging. The test is with the test code executing in the container. I'd like to propose these constants instead: public enum RunModeType { /** * In LOCAL mode, the @Deployment is processed and deployed to the Container, * but the test is not executed inside the container. It's local to the test runner. */ LOCAL, /** * In IN_CONTAINER mode, the @Deployment is processed and deployed to the container along side the test * case and the test case is executed inside the container.<br/> * This is the default mode when none specified. */ IN_CONTAINER } Perhaps I'm just thinking about it wrong, but I just can't get my mind to believe that @RunMode(REMOTE) means that the test case is running in the container. I get how it is technically correct, but human tendency leads me to believe we are going to have to constantly clarify this. @RunMode(IN_CONTAINER) makes it clear that the test is getting relocated to the container. (I'm even open to changing LOCAL to NORMAL if you think it helps the terminology) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-99) JBoss related classes should be named JBoss(capital B)

by Aslak Knutsen (JIRA)

JBoss related classes should be named JBoss(capital B) ------------------------------------------------------ Key: ARQ-99 URL: https://jira.jboss.org/jira/browse/ARQ-99 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Alpha1 Reporter: Aslak Knutsen All Classes that has JBoss in the name should be using capital B. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-71) Should be able to run the test case locally

by Aslak Knutsen (JIRA)

Should be able to run the test case locally ------------------------------------------- Key: ARQ-71 URL: https://jira.jboss.org/jira/browse/ARQ-71 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen It should be possible to just use Arquillian for packaging/deployment for a test case without actually running the test case inside the container. Needed to ie support testing of Servlets, or EJB Remoting -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-70) Support Method argument injection

by Aslak Knutsen (JIRA)

Support Method argument injection --------------------------------- Key: ARQ-70 URL: https://jira.jboss.org/jira/browse/ARQ-70 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Assignee: Aslak Knutsen TestEnrichers should be extended to support method argument injection. {code} @Test public void shouldBeAbleToInjectArguments(@Resource, @EJB, MyCDIBean) throws Exception { } {code} e.g: {code} public interface TestEnricher { /** * Extension point to add features to the test method arguments. * * IE. Argument injection * * @param method * @return Object[] that match the Field[] indexes. Return null at a specific index value if it can't be handeled. */ Object[] resolve(Method method); } {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-96) Create an embedded container for OpenWebBeans

by Dan Allen (JIRA)

Create an embedded container for OpenWebBeans --------------------------------------------- Key: ARQ-96 URL: https://jira.jboss.org/jira/browse/ARQ-96 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 1.0.0.Alpha2 Create an embedded container implementation for OpenWebBeans akin to the Weld embedded container. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-114) DeployableContainer and TestEnrichers need to share state

by Aslak Knutsen (JIRA)

DeployableContainer and TestEnrichers need to share state --------------------------------------------------------- Key: ARQ-114 URL: https://jira.jboss.org/jira/browse/ARQ-114 Project: Arquillian Issue Type: Task Components: Deployable Containers SPI, Runtime Enricher SPI Reporter: Aslak Knutsen Assignee: Aslak Knutsen When working with embedded containers, the test enrichers need to access the container or container related apis. Open up the DeployableContainer and TestEnricher spi to have access to the Context. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-93) No-interface session beans are not supported

by Juergen Zimmermann (JIRA)

No-interface session beans are not supported -------------------------------------------- Key: ARQ-93 URL: https://jira.jboss.org/jira/browse/ARQ-93 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Alpha1 Reporter: Juergen Zimmermann According to the JNDI naming convention at http://docs.jboss.org/arquillian/reference/1.0.0.Alpha1/en-US/html/enrich... no-interface session beans cannot be tested directly. Their JNDI suffix is .../no-interface instead of .../local or .../remote. To use no-interface session beans with JBossAS 6.0.0.M2 it is recommended to use jboss-ejb3-nointerface-impl-1.0.0-alpha-5.jar from http://repository.jboss.com/maven2/org/jboss/ejb3/nointerface/jboss-ejb3-... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-69) Redesign the test framework adaptor

by Aslak Knutsen (JIRA)

Redesign the test framework adaptor ----------------------------------- Key: ARQ-69 URL: https://jira.jboss.org/jira/browse/ARQ-69 Project: Arquillian Issue Type: Task Components: Core, Documentation, JUnit, TestNG Reporter: Aslak Knutsen Assignee: Aslak Knutsen Too much of the Arquillian core responsibility is handed out to the Test Framework integration code. Redesign to a more event/lifecycle based integration. The DeployableTestBuilder should return a appropriate impl depending on in container or not. {code} public interface DeployableTestRunner { public void beforeSuite() throws LifecycleException public void afterSuite() throws LifecycleException public void beforeClass(Class<?> testClass) throws DeploymentException public void afterClasss(Class<?> testClass) throws DeploymentException public void before(Class<?> testClass, Method testMethod) public void after(Class<?> testClass, Method testMethod) public TestResult test(TestMethodExecutor testMethodExecutor) } {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2010