From 806af3da0f3ece02143bcb89b1eb2d195c4d36e6 Mon Sep 17 00:00:00 2001
From: Kyle Winkelman <39207896+kyle-winkelman@users.noreply.github.com>
Date: Mon, 15 Jan 2024 09:40:16 -0600
Subject: [PATCH] Add extensionScanningEnabled option to @WireMockTest. (#242)

---
 _docs/junit-jupiter.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/_docs/junit-jupiter.md b/_docs/junit-jupiter.md
index 2645fb75..0139f260 100644
--- a/_docs/junit-jupiter.md
+++ b/_docs/junit-jupiter.md
@@ -79,6 +79,18 @@ public class HttpsFixedPortDeclarativeWireMockTest {
 }
 ```
 
+### Enabling Extension Scanning
+
+When [extending WireMock via service loading](extending-wiremock.md#extension-registration-via-service-loading), it may
+be helpful to have WireMock scan for extensions automatically via the `extensionScanningEnabled` parameter.
+
+```java
+@WireMockTest(extensionScanningEnabled = true)
+public class ExtensionScanningDeclarativeWireMockTest {
+    ...
+}
+```
+
 ## Advanced usage - programmatic
 
 Invoking the extension programmatically with `@RegisterExtension` allows you to run any number of WireMock instances and provides full control