From 09d3dda57253fe33b1eaaacf442dd536961e866b Mon Sep 17 00:00:00 2001 From: Stefano Cordio Date: Wed, 28 Jan 2026 15:26:59 +0100 Subject: [PATCH 1/2] Document naming convention for custom test-scoped starters See gh-49014 Signed-off-by: Stefano Cordio --- .../pages/features/developing-auto-configuration.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc index c278e5396a9..b2331f0000b 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc @@ -249,6 +249,8 @@ At the same time, others can rely only on the `autoconfigure` module and craft t If the auto-configuration is relatively straightforward and does not have optional features, merging the two modules in the starter is definitely an option. +When testing "acme" features, you may need test-specific auto-configuration, for example, to replace external dependencies with in-memory alternatives. +A separate test-scoped starter can be created for this purpose, following the same principles. [[features.developing-auto-configuration.custom-starter.naming]] @@ -262,6 +264,7 @@ As a rule of thumb, you should name a combined module after the starter. For example, assume that you are creating a starter for "acme" and that you name the auto-configure module `acme-spring-boot` and the starter `acme-spring-boot-starter`. If you only have one module that combines the two, name it `acme-spring-boot-starter`. +If "acme" also has a test-scoped starter, name it `acme-spring-boot-starter-test`. [[features.developing-auto-configuration.custom-starter.configuration-keys]] From 21c7f7c7e78b992ab8aa18f1b4379c7b63dc2bc5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Nicoll?= Date: Thu, 29 Jan 2026 11:26:24 +0100 Subject: [PATCH 2/2] Polish "Document naming convention for custom test-scoped starters" See gh-49014 --- .../pages/features/developing-auto-configuration.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc index b2331f0000b..ea93b51aed0 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/features/developing-auto-configuration.adoc @@ -249,7 +249,8 @@ At the same time, others can rely only on the `autoconfigure` module and craft t If the auto-configuration is relatively straightforward and does not have optional features, merging the two modules in the starter is definitely an option. -When testing "acme" features, you may need test-specific auto-configuration, for example, to replace external dependencies with in-memory alternatives. +When testing "acme" features, you may need test-specific auto-configurations. +For example, you could offer a way to replace external dependencies with in-memory alternatives. A separate test-scoped starter can be created for this purpose, following the same principles.