Assert execution order in validation tests with type cycles (#443)

The method execution order in type cycles depends on the JVM
implementation. This validation ensure our test setup produce the
required scenarios.

1 files changed, 23 insertions, 0 deletions

diff --git a/org.jacoco.core.test/src/org/jacoco/core/test/validation/targets/Stubs.java b/org.jacoco.core.test/src/org/jacoco/core/test/validation/targets/Stubs.java
index eae387b7..c4cb5d48 100644
--- a/org.jacoco.core.test/src/org/jacoco/core/test/validation/targets/Stubs.java
+++ b/org.jacoco.core.test/src/org/jacoco/core/test/validation/targets/Stubs.java
@@ -11,6 +11,9 @@
  *******************************************************************************/
 package org.jacoco.core.test.validation.targets;
 
+import java.util.ArrayList;
+import java.util.List;
+
 /**
  * Collection of stub methods that are called from the coverage targets. *
  */
@@ -117,4 +120,24 @@ public class Stubs {
 	public static void noexec(Runnable task) {
 	}
 
+	/**
+	 * List of logged events. Using a static member here works as this class is
+	 * loaded in a new class loader for every test case.
+	 */
+	private static List<String> events = new ArrayList<String>();
+
+	/**
+	 * Records a event with the given id for later verification.
+	 */
+	public static void logEvent(String id) {
+		events.add(id);
+	}
+
+	/**
+	 * Returns a list of all recorded events in the sequence of recording.
+	 */
+	public static List<String> getLogEvents() {
+		return events;
+	}
+
 }