Talk:OrderOfElements
From APIDesign
(Difference between revisions)
(Once the comment is enough) |
m (Reverted edits by 46.29.248.193 (Talk); changed back to last version by JaroslavTulach) |
||
(2 intermediate revisions not shown.) | |||
Line 13: | Line 13: | ||
--[http://michael-bien.com mbien] 01:15, 23 August 2011 (CEST) | --[http://michael-bien.com mbien] 01:15, 23 August 2011 (CEST) | ||
</div> | </div> | ||
+ | |||
+ | Hello Michael, I've been told that [[TestNG]] supports ordering of tests. Kent replied to me that methods in [[JUnit]] test class should rather be independent. As far as the RFE for [[JUnit]] goes - right, [[Jesse]] created [https://github.com/KentBeck/junit/pull/293 one]. Actually, what [[Jesse]] suggest is to sort test methods alphabetically. | ||
+ | |||
+ | --[[User:JaroslavTulach|JaroslavTulach]] 16:14, 27 August 2011 (UTC) |
Current revision
Comments on OrderOfElements <comments />
mbien said ...
Hello Michael, I've been told that TestNG supports ordering of tests. Kent replied to me that methods in JUnit test class should rather be independent. As far as the RFE for JUnit goes - right, Jesse created one. Actually, what Jesse suggest is to sort test methods alphabetically.
--JaroslavTulach 16:14, 27 August 2011 (UTC)
looks like a RFE for junit to me. I agree the execution order of test methods should not change between runs. something like @After("test5") or @Test("2") would solve it in most cases IMO. I always had the habit to sort the result of getMethods() alphabetically (method name+parameters concatenated) in my libs (mostly code generators) since i knew this might happen some time in the future.
thanks for the heads up!
--mbien 01:15, 23 August 2011 (CEST)