[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
[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
[JBoss JIRA] Created: (ARQ-506) Support more complex property types in container configuration
by Gerhard Poul (JIRA)
Support more complex property types in container configuration
--------------------------------------------------------------
Key: ARQ-506
URL: https://issues.jboss.org/browse/ARQ-506
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Configuration
Reporter: Gerhard Poul
Priority: Optional
It might sometimes be helpful to support arbitrary property lists within an arquillian configuration, such as when we want to make it possible to pass properties to the underlying container implementations, but that have no effect on the behavior of the arquillian-container-implementation itself.
This is not to replace, but to augment the current configuration capability, such that we can provide something like the following in an arquillian.xml:
<container qualifier="someQualifier" default="true">
<configuration>
<propertyList name="somePropertyName">
<propertyEntry name="somePropertyEntryName" type="java.lang.String" value="someValue" />
<propertyEntry name="somePropertyEntryName2" type="java.lang.Integer" value="1234" />
...
</propertyList>
<property name="someOtherProperty">someValue</property>
</configuration>
</container>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (ARQ-473) DeployableContainer should not be restricted to only deploy Descriptors or Archives
by Aslak Knutsen (JIRA)
DeployableContainer should not be restricted to only deploy Descriptors or Archives
-----------------------------------------------------------------------------------
Key: ARQ-473
URL: https://issues.jboss.org/browse/ARQ-473
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation, Deployable Containers SPI
Affects Versions: 1.0.0.CR1
Reporter: Aslak Knutsen
Fix For: 1.1.0.CR1
To open up for more specialized Containers we should support some type of 'WildCard' Deploy.
Possible by having a Annotation driven DeployableContainer, e.g.
@Deploy
public SomethingExposedInContext(SomeRandomOtherType type)
This will let us e.g. deploy Files/ Images etc directly for non Java/EE type Containers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (ARQ-417) Support maven deployments
by Adrian Cole (JIRA)
Support maven deployments
-------------------------
Key: ARQ-417
URL: https://issues.jboss.org/browse/ARQ-417
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Configuration
Reporter: Adrian Cole
Microdeployments via ShrinkWrap are a nimble deployment mechanism that allows developers to test bytecode skipping the build. Another usecase is to have ARQ in a CI loop, testing artifacts post-deploy. For this sort of scenario, it would be useful to reuse test cases from the microdeployments, but have them leveraged against code pulled from maven artifacts published in a prior step.
For example, we could have an @Maven annotation which could define the coordinates of an ear file, and place that on a test scenario that performs the war, ejb, cdi, etc tests of from the dependent modules.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (ARQ-480) Create a Notification SPI
by Aslak Knutsen (JIRA)
Create a Notification SPI
-------------------------
Key: ARQ-480
URL: https://issues.jboss.org/browse/ARQ-480
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation, Runtime Enricher SPI
Affects Versions: 1.0.0.Final
Reporter: Aslak Knutsen
Fix For: 1.1.0.Beta1
There should be a way for SPI impls to communicate with executor about what they have done outside of throwing exception.
e.g. TestEnrcihers
* EJBEnricher ran first and couldn't find a specific @EJB, but CDI runs after and can.
** EJBEnricher should not fail on his attempt, but should report what he tried and where he failed
** CDI Enricher should be executed regardless of EJBEnrichers outcome
** Summarize in the end to compare if we have a full Enriched Object
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month