OrderOfElements

From APIDesign

Revision as of 09:30, 22 August 2011 (edit) JaroslavTulach (Talk | contribs) ← Previous diff		Revision as of 09:42, 22 August 2011 (edit) (undo) JaroslavTulach (Talk | contribs) (→JUnit and Switch to JDK7) Next diff →
Line 2:		Line 2:
	== [[JUnit]] and Switch to [[JDK]]7 ==		== [[JUnit]] and Switch to [[JDK]]7 ==
		+
		+	[[NetBeans]] is using [[JUnit]] a lot for own internal testing. For historical reasons majority of our existing tests is written against [[JUnit]]3 and even newly created tests continue to be based on the 3.x style. I want to mention this at the beggining, as I am not sure if the same problem we are facing now influences [[JUnit]]4 style tests (although I believe it does).

---

Revision as of 09:42, 22 August 2011

Runtime BackwardCompatibility can be significantly influenced by changing the order of elements in a Collection or in an Array. Sure, some people would argue that depending on the order of items as served by HashSet.iterator() is unreasonable (and there is no doubt about that), however there are less obvious cases.

JUnit and Switch to JDK7

NetBeans is using JUnit a lot for own internal testing. For historical reasons majority of our existing tests is written against JUnit3 and even newly created tests continue to be based on the 3.x style. I want to mention this at the beggining, as I am not sure if the same problem we are facing now influences JUnit4 style tests (although I believe it does).

TBD