Configurable scenario supplier (#301)

* Updated extension with a configurable scenario supplier

* Added a function which only takes a ScenarioSupplier in addition to the one which takes a Class and ScenarioSupplier

* Added / updated javadoc

* Updated the API surface file

Author: compscidr

instrumentation/compose/api/compose.api

@@ -13,7 +13,8 @@ public final class de/mannodermaus/junit5/compose/AndroidComposeExtension : de/m
 }
 
 public final class de/mannodermaus/junit5/compose/AndroidComposeExtensionKt {
-	public static final fun createAndroidComposeExtension (Ljava/lang/Class;)Lde/mannodermaus/junit5/compose/AndroidComposeExtension;
+	public static final fun createAndroidComposeExtension (Ljava/lang/Class;Lkotlin/jvm/functions/Function0;)Lde/mannodermaus/junit5/compose/AndroidComposeExtension;
+	public static synthetic fun createAndroidComposeExtension$default (Ljava/lang/Class;Lkotlin/jvm/functions/Function0;ILjava/lang/Object;)Lde/mannodermaus/junit5/compose/AndroidComposeExtension;
 	public static final fun createComposeExtension ()Lde/mannodermaus/junit5/compose/ComposeExtension;
 }
 

instrumentation/compose/src/main/java/de/mannodermaus/junit5/compose/AndroidComposeExtension.kt

@@ -51,17 +51,26 @@ public inline fun <reified A : ComponentActivity> createAndroidComposeExtension(
  * for field injection. Prefer this over [createComposeExtension] if your tests require a custom Activity.
  * This is usually the case for tests where the Compose content is set by that Activity, instead of
  * via [ComposeContext.setContent], provided through the extension. Make sure that you add the provided
- * Activity to your app's manifest file.
+ * Activity to your app's manifest file. This variant allows you to provide a custom [ActivityScenario]
+ * which is useful in cases where you may want to launch an activity with a custom intent, for example.
  */
 @ExperimentalTestApi
-public fun <A : ComponentActivity> createAndroidComposeExtension(
-    activityClass: Class<A>
-): AndroidComposeExtension<A> {
-    return AndroidComposeExtension(
-        scenarioSupplier = {
-            ActivityScenario.launch(activityClass)
-        }
-    )
+public inline fun <reified A : ComponentActivity> createAndroidComposeExtension(noinline scenarioSupplier: () -> ActivityScenario<A>): AndroidComposeExtension<A> {
+    return createAndroidComposeExtension(A::class.java, scenarioSupplier)
+}
+
+/**
+ * Factory method to provide a JUnit 5 extension for Compose using its [RegisterExtension] API
+ * for field injection. Prefer this over [createComposeExtension] if your tests require a custom Activity.
+ * This is usually the case for tests where the Compose content is set by that Activity, instead of
+ * via [ComposeContext.setContent], provided through the extension. Make sure that you add the provided
+ * Activity to your app's manifest file. You may also provide an optional [ActivityScenario] supplier
+ * which is useful in cases where you may want to launch an activity with a custom intent,for example.
+ */
+@ExperimentalTestApi
+public fun <A : ComponentActivity> createAndroidComposeExtension(activityClass: Class<A>,
+                                                                 scenarioSupplier: () -> ActivityScenario<A> = { ActivityScenario.launch(activityClass) }): AndroidComposeExtension<A> {
+    return AndroidComposeExtension(scenarioSupplier)
 }
 
 /**