May 2011 - arquillian-issues - Jboss List Archives

[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

11 years, 12 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-415) Use Seam Solder instead of Weld Extensions

by Hendy Irawan (JIRA)

Use Seam Solder instead of Weld Extensions ------------------------------------------ Key: ARQ-415 URL: https://issues.jboss.org/browse/ARQ-415 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Examples Affects Versions: 1.0.0.Alpha5 Reporter: Hendy Irawan Use Seam Solder instead of Weld Extensions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-74) Base test deployment on project in which test is run

by Pete Muir (JIRA)

Base test deployment on project in which test is run ---------------------------------------------------- Key: ARQ-74 URL: https://jira.jboss.org/jira/browse/ARQ-74 Project: Arquillian Issue Type: Feature Request Reporter: Pete Muir A common testing scenario will be to deploy the artifact generated by the current project, and run tests against it. For example, say my project was building a war, I want to be able to deploy that war, inserting the test case and any beans into the deployment, and have my tests run. In this case the deep control of the classpath through shrinkwrap is getting in the way. -- 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

12 years

3
8
0 / 0

[JBoss JIRA] Created: (ARQ-160) Improve Exception messages / handling

by Aslak Knutsen (JIRA)

Improve Exception messages / handling ------------------------------------- Key: ARQ-160 URL: https://jira.jboss.org/browse/ARQ-160 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen We should create an Exception message id set linking to wiki articles/faq about the specific error case. This will help on the user experience and exposure of jboss.org -- 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

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-224) Create Wiki entries for every Error Message id

by Aslak Knutsen (JIRA)

Create Wiki entries for every Error Message id ---------------------------------------------- Key: ARQ-224 URL: https://jira.jboss.org/browse/ARQ-224 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Every Exception ID Arquillian defines should be mapped to a open wiki page where we can add description about the exception, why and how to fix it etc.. -- 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

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-232) Redesign Servlet protocol to be more human friendly

by Aslak Knutsen (JIRA)

Redesign Servlet protocol to be more human friendly --------------------------------------------------- Key: ARQ-232 URL: https://jira.jboss.org/browse/ARQ-232 Project: Arquillian Issue Type: Feature Request Components: Test Protocol SPIs and Implementation Reporter: Aslak Knutsen Priority: Minor We should redesign the Servlet communication protocol to be more Rest api like. This will make it easier for humans to execute tests outside of the Arquillian Client and opens for other clients to communicate with the test. http://arquillian.pastebin.com/XHsfaycJ Add support for html output -- 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

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-442) Change Examples modules to a container sanity test suite

by Aslak Knutsen (JIRA)

Change Examples modules to a container sanity test suite -------------------------------------------------------- Key: ARQ-442 URL: https://issues.jboss.org/browse/ARQ-442 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta1 Reporter: Aslak Knutsen The current examples modules should be recreated as a sanity test suite for the containers. Currently all containers have their own simple tests for validating the functionality. These container tests should be merged with the examples and created as a test suite. The test suite needs to be split up by package / module based on EE v / technology to support all containers(easy maven filtering). The containers should depend on this test suite and not the other way around. todo: research how to include a external module as a test suite for a module. (copy-dependencies / extract ? / container config etc) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-141) Add option to export the generated Archive to inspect the final deployment

by Aslak Knutsen (JIRA)

Add option to export the generated Archive to inspect the final deployment -------------------------------------------------------------------------- Key: ARQ-141 URL: https://jira.jboss.org/browse/ARQ-141 Project: Arquillian Issue Type: Task Components: Configuration, Documentation Reporter: Aslak Knutsen It is useful for debugging to have Arquillian export the Archive it is about to deploy, specially in IN_CONTAINER mode. Create a ArchiveExporter EventHandler on class level and make the export folder configurable. If option is not set: don't export -- 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

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-350) Map client events 1 to 1 with container events

by Aslak Knutsen (JIRA)

Map client events 1 to 1 with container events ---------------------------------------------- Key: ARQ-350 URL: https://issues.jboss.org/browse/ARQ-350 Project: Arquillian Issue Type: Feature Request Components: Base Implementation, Test Protocol SPIs and Implementation Reporter: Aslak Knutsen We should redo how the test execution lifecycles happen. In the current impl the flow is: Client(BeforSuite, BeforeClass, Before) -> Container(BeforSuite, BeforeClass, Before, Test, After, AfterClass, AfterSuite) -> Client(After, AfterClass, AfterSuite) We should map these 1 to 1 with the incontainer execution and keep the test instance alive between the calls. Client(BeforeClass) -> Container(BeforeClass) Client(Before) -> Container(Before) .. This way the execution is closer to how it normally would be, and extensions can interact with the Container/Environment or Client in the appropriate lifecycles more naturally. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-271) TestEnricher should be called in @BeforeClass as well

by Thomas Diesler (JIRA)

TestEnricher should be called in @BeforeClass as well ----------------------------------------------------- Key: ARQ-271 URL: https://jira.jboss.org/browse/ARQ-271 Project: Arquillian Issue Type: Feature Request Reporter: Thomas Diesler The TestEnricher API could be extended such that static fields can be initialized. @Inject public static BundleContext context; @BeforeClass public static void beforeClass() { System.out.println("BeforeClass: " + context); } There would be two calls to TestEnricher. #1 After test class load, but before a call to @BeforeClass. #2 After instantiation of the test class, but before a call to @Before (#2 is the current behaviour) -- 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

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2011