[JBoss JIRA] (ARQ-734) Filter TestClass based on @OperatesOnDeployment during deploy
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-734:
---------------------------------
Summary: Filter TestClass based on @OperatesOnDeployment during deploy
Key: ARQ-734
URL: https://issues.jboss.org/browse/ARQ-734
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation
Affects Versions: 1.0.0.CR7
Reporter: Aslak Knutsen
When using Multiple incontainer Deployments with different Content in combination with @OperatesOnDeployment @Tests might fail due to CNFE.
CNFE is thrown by the Container because the TestClass is refers to Classes from the 'other' deployment and can't be loaded, even tho they are not executed.
Arquillian should Filter and Rewrite the TestClass before it is deployed so only the @Test methods that are targeted to a specific Deployment are visible runtime.
Note:
javaassist is a very common lib and version conflicts are easy to occur. Shard javassist under a org.jboss.arq namespace?
--
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
12 years, 6 months
[JBoss JIRA] (ARQ-880) Allow extensions create new child tests with dynamic nature
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQ-880:
------------------------------
Summary: Allow extensions create new child tests with dynamic nature
Key: ARQ-880
URL: https://issues.jboss.org/browse/ARQ-880
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation
Affects Versions: 1.0.0.Final
Reporter: Lukáš Fryč
There are situations where it's convenient to load the tests into the current suite.
You can then reuse the test framework specific integration tools like IDE integration, reporters and continuous integration
to run the test logic outside the Java ecosystem.
----
Test frameworks doesn't have any generic integration points for this job.
To allow Arquillian extension writers having as easy job as possible,
SPI should be designed which would allow to register new tests in framework-specific test runners.
----
SPI Proposal:
Arquillian fires {{LocateChildren}} event to allow extension populate suite with "dynamic" tests.
{{LocateChildren}} event can be populated with {{ChildTestClass}} (having many {{ChildTestMethod}}).
Arquillian fires {{TestChild}} to allow extension invoke the use-case-specific test logic for each registered {{ChildTestMethod}}.
--
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
12 years, 6 months
[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, 6 months