11:13 a.m.
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:01 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-474:
-----------------------------------
Any suggestions to API ?
@InOrder(Integer) // doesn't mean anything..
or
@DependsOn("otherMethodName") // has problems with refactoring
Others?
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:05 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Prabhat Jha commented on ARQ-474:
---------------------------------
I was thinking more in the line of @DependsOn("otherMethodName").
What do you mean by does not mean anything? Are you talking the annotation name
"InOrder"?
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:36 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-474:
-----------------------------------
no I meant more semantics, looking at @DependsOn("m") says that this one should
come after "m", InOrder(1) alone doesn't say much besides 1, so you have to
look around what is 0 or 2.
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:25 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Martin Gencur commented on ARQ-474:
-----------------------------------
How about providing an annotation, lets say, @Ordered with which a whole test class could
be annotated and then the test methods would be ordered according to the order in which
they are written in the test class (from top->down). Do you think it would be
possible?
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:35 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Martin Gencur commented on ARQ-474:
-----------------------------------
Hmm, the method Class.getDeclaredMethods returns an unsorted list of class' methods so
methods could be sorted only in a different way, for example alphabetically. But I
don't know if this is reasonable.
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:33 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-474:
-----------------------------------
The Java Language spec does not define any order of methods or fields . There is no direct
relation between source and compiled v when using reflection. It just some times happen to
be that way. :)
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Ondrej Zizka commented on ARQ-474:
----------------------------------
+1 on @InOrder, only I'd call it @TestOrder.
Reasoning:
1) I'd prefer to cope with numbers than copying method names, which, as you noted, may
change.
2) Also, adding @TestOrder(1) might be easier to support in IDEs - you just add annotate
all test methods with increasing number, instead of adding depends on
3) Using @DependsOn for ordering would be a bit misusing of it...
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:51 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen edited comment on ARQ-474 at 7/1/11 3:51 PM:
-----------------------------------------------------------
What about the non ordered ones? executed before or after?
Default order is 0, then you can order as you like + or - ?
was (Author: aslak):
What about the non ordered once? executed before or after?
Default order is 0, then you can order as you like + or - ?
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:51 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-474:
-----------------------------------
What about the non ordered once? executed before or after?
Default order is 0, then you can order as you like + or - ?
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
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] (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-474:
------------------------------
Assignee: Aslak Knutsen
Fix Version/s: 1.0.0.Final
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Assignee: Aslak Knutsen
Fix For: 1.0.0.Final
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
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
10:51 a.m.
New subject: [JBoss JIRA] (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen edited comment on ARQ-474 at 11/24/11 11:51 AM:
--------------------------------------------------------------
pushed upstream, @InSequence\(n\)
was (Author: aslak):
pushed upstream, @InSequence(n)
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Assignee: Aslak Knutsen
Fix For: 1.0.0.Final
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
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
10:51 a.m.
New subject: [JBoss JIRA] (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen resolved ARQ-474.
-------------------------------
Resolution: Done
pushed upstream, @InSequence(n)
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Assignee: Aslak Knutsen
Fix For: 1.0.0.Final
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
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
5:39 a.m.
New subject: [JBoss JIRA] (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-474:
------------------------------
Fix Version/s: 1.0.0.CR6
(was: 1.0.0.Final)
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Assignee: Aslak Knutsen
Fix For: 1.0.0.CR6
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
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
8:58 a.m.
New subject: [JBoss JIRA] (ARQ-474) provide a mechanism to order the test runs
[
https://issues.jboss.org/browse/ARQ-474?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-474.
-----------------------------
provide a mechanism to order the test runs
------------------------------------------
Key: ARQ-474
URL: https://issues.jboss.org/browse/ARQ-474
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Test Harness Integration
Affects Versions: 1.0.0.Beta1
Reporter: Prabhat Jha
Assignee: Aslak Knutsen
Fix For: 1.0.0.CR6
Currently there exists annotation for deployment ordering but there does not exist a way
to control the order in which one wants to run the test. TestNG does have ordering via
depends method but JUnit does not. Usually, it's recommended to not have a dependency
of test order but in case of clustering and data grid testing where you want to verify
replication, it makes sense to have that.
Please add a fix version which makes a sense based on the roadmap you have.
--
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
4799
days inactive
4962
days old
arquillian-issues@lists.jboss.org
14 comments
8 participants
participants (8)
-
Aslak Knutsen (Closed) (JIRA) -
Aslak Knutsen (Issue Comment Edited) (JIRA)
-
Aslak Knutsen (JIRA)
-
Aslak Knutsen (Resolved) (JIRA)
-
Aslak Knutsen (Updated) (JIRA)
-
Martin Gencur (JIRA)
-
Ondrej Zizka (JIRA)
-
Prabhat Jha (JIRA)