[JBoss JIRA] Created: (ARQ-287) Add support for filtering tests based on required execution environment
12:57 a.m.
Add support for filtering tests based on required execution environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Container.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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:59 a.m.
New subject: [JBoss JIRA] Work started: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Work on ARQ-287 started by Dan Allen.
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Container.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
2:52 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-287:
-------------------------------
Tracking branches:
proposal A: http://github.com/mojavelinux/arquillian/tree/ARQ-287-proposalA
proposal B: http://github.com/mojavelinux/arquillian/tree/ARQ-287-proposalB
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Container.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
2:54 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Dan Allen updated ARQ-287:
--------------------------
Description:
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
was:
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Container.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
2:56 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-287:
-------------------------------
In both proposals, the include/exclude surefire configuration has been completely replaces
with a required execution environment annotation on each test class. Note, however, that
this feature only works for JUnit until we get support in TestNG to veto the test
(currently a work in progress).
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
11:22 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-287:
-----------------------------------
Both proposals are based on @ProvidedBy which is a hard coding of package name expressions
for the given Containers. This approach does not scale at all. If at all, this should be
moved down to the Container.
But then the issues becomes, who am i(the container dev) to force no support for CDI in
JBoss 5. Someone might have hacked it up.. The users knowns better then we do what the
containers he is running against supports.
This approach also makes the api 'dependent' on technology related terms like EJB,
EE, CDI, etc.. (technology come and go, arquillian is here to stay.. ;)
A much simpler approach would be to let the user define some sort of group names that make
sense to him and his test suite, where he could add filtering of the groups e.g. in
arquillian.xml pr Container.
e.g.
@Group("Messaging-BackendSystem-1-Test")
@RunWith(Arquillian.class)
public test MyTest() {}
arquillian.xml:
<jboss:container>
<group>Messaging-BackendSystem-1-Test</group>
..
</jboss:container>
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
11:24 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-287 at 9/12/10 12:24 PM:
-------------------------------------------------------------
Both proposals are based on @ProvidedBy which is a hard coding of package name expressions
for the given Containers. This approach does not scale at all. If at all, this should be
moved down to the Container.
But then the issues becomes, who am i(the container dev) to force no support for CDI in
JBoss 5. Someone might have hacked it up.. The users knowns better then we do what the
containers he is running against supports.
This approach also makes the api 'dependent' on technology related terms like EJB,
EE, CDI, etc.. (technology come and go, arquillian is here to stay.. ;)
A much simpler approach would be to let the user define some sort of group names that make
sense to him and his test suite, where he could add filtering of the groups e.g. in
arquillian.xml pr Container.
e.g.
@Group("Messaging-BackendSystem-1-Test")
@RunWith(Arquillian.class)
public test MyTest() {}
arquillian.xml:
<jboss:container id="messaging-backend">
<group>Messaging-BackendSystem-1-Test</group>
..
</jboss:container>
<jboss:container id="messaging-front">
<group>Messaging-FrontendSystem-1-Test</group>
..
</jboss:container>
Note: multiple containers of the same type can be added, but represent different things to
the user. All EE6 tests are not necessarily fit for all configured EE servers.
was (Author: aslak):
Both proposals are based on @ProvidedBy which is a hard coding of package name
expressions for the given Containers. This approach does not scale at all. If at all, this
should be moved down to the Container.
But then the issues becomes, who am i(the container dev) to force no support for CDI in
JBoss 5. Someone might have hacked it up.. The users knowns better then we do what the
containers he is running against supports.
This approach also makes the api 'dependent' on technology related terms like EJB,
EE, CDI, etc.. (technology come and go, arquillian is here to stay.. ;)
A much simpler approach would be to let the user define some sort of group names that make
sense to him and his test suite, where he could add filtering of the groups e.g. in
arquillian.xml pr Container.
e.g.
@Group("Messaging-BackendSystem-1-Test")
@RunWith(Arquillian.class)
public test MyTest() {}
arquillian.xml:
<jboss:container>
<group>Messaging-BackendSystem-1-Test</group>
..
</jboss:container>
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
5:10 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-287:
-------------------------------
Please review the formal proposal: https://community.jboss.org/message/561676
I want to repeat my note here that I strongly oppose doing any of this in XML-based
configuration. I want the information about what the test requires in the test class. I am
open, however, to considering other ways in which containers are linked to execution
environments. Though we want to avoid annotation scanning or burdening the developer w/
configuration.
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
5:20 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-287:
-------------------------------
Btw, I disagree that the design proposed does not scale. The built-in environments are
merely a convenience. Developers have the option of combining ExecutionEnvironment and
@ProvidedBy to define a custom execution environment. It's totally extensible.
For instance, some of the Arquillian JUnit examples can only be run on JBoss AS, so we
define it as an execution environment:
@ProvidedBy(
containers =
{
"~
org\\.jboss\\.arquillian\\.container\\.jbossas\\.(managed|remote|embedded)_5(_[0-9]+)*"
}
)
public final class JBossAS6Container implements ExecutionEnvironment {}
There is no reason why the developer can't come up with any combination they need.
I'm just not all the comfortable with how we are referencing containers. I'd like
that to be a cleaner association. Perhaps to be discussed in a seperate JIRA, i'd like
to have containers declare a unique identifier, the common name, the vendor and the
supported version range.
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
5:56 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://jira.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-287:
-----------------------------------
by scale I mean, we need arquillian-api changes every time a container/enricher is
added/changed/removed..
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://jira.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
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
5:25 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://issues.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-287:
------------------------------
Fix Version/s: 1.0.0.CR1
(was: 1.0.0.Beta1)
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://issues.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.CR1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-287) Add support for filtering tests based on required execution environment
[
https://issues.jboss.org/browse/ARQ-287?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-287:
------------------------------
Fix Version/s: 1.1.0.Beta1
(was: 1.0.0.CR1)
Add support for filtering tests based on required execution
environment
-----------------------------------------------------------------------
Key: ARQ-287
URL: https://issues.jboss.org/browse/ARQ-287
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.1.0.Beta1
Allow the developer to declaratively specify the execution environment required for a
given test to function. Then, Arquillian should filter out tests that require an execution
environment that the target container doesn't provide. (In other words, only execute a
test case if the target container provides the execution environment the test requires).
To support this feature, we need to introduce the concept of an execution environment
definition into the API and a mechanism for indicating which containers provide a given
execution environment. The developer experience will be something like:
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@RequiresEnvironment(JavaEE6Environment.class)
public @interface RequiresJavaEE6 {}
@RunWith(Arquillian.class)
@RequiresJavaEE6
public class MyTestCase { ... }
or
@RunWith(Arquillian.class)
@RequiresEnvironment(JavaEE6Environment.class)
public class MyTestCase { ... }
Formal proposals and prototypes will be submitted as branches in github.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4954
days inactive
5221
days old
arquillian-issues@lists.jboss.org
11 comments
2 participants
participants (2)
-
Aslak Knutsen (JIRA) -
Dan Allen (JIRA)