Copybara ❤️: Add test sizes to correctly timeout onboarding tests

CL: cl/580509534
PiperOrigin-RevId: 580509534
Change-Id: I855a9c9f315840ae28e23d5a46e24ce29402e344

1 files changed, 20 insertions, 1 deletions

diff --git a/src/com/android/onboarding/contracts/annotations/OnboardingNode.kt b/src/com/android/onboarding/contracts/annotations/OnboardingNode.kt
index 3ea43f6..17c9645 100644
--- a/src/com/android/onboarding/contracts/annotations/OnboardingNode.kt
+++ b/src/com/android/onboarding/contracts/annotations/OnboardingNode.kt
@@ -14,13 +14,32 @@ annotation class OnboardingNode(
   val name: String,
 
   /** True if this is a node which presents a UI to the user. */
-  val hasUi: HasUi
+  val hasUi: HasUi,
+
+  /** The type of specification given for this node. */
+  val specificationType: SpecificationType = SpecificationType.LIGHT
 ) {
   enum class HasUi {
     NO,
     YES,
     YES_TEMPORARILY
   }
+
+  enum class SpecificationType {
+    /**
+     * This means that full Javadoc is provided, all arguments are fully defined, documented and
+     * typed (no undefined Bundles or Intents), and return values are properly defined and typed.
+     */
+    V1,
+
+    /**
+     * No requirements.
+     *
+     * Most "Light" nodes will be lacking Javadoc, and using Intents and Bundles as arguments and
+     * return values.
+     */
+    LIGHT
+  }
 }
 
 const val MAX_NODE_NAME_LENGTH: Int = 40