Link to SpringProperties Javadoc from the Testing chapter

Closes gh-26492

Author: sbrannen

src/docs/asciidoc/testing.adoc

@@ -1846,7 +1846,9 @@ constructor takes precedence over both `@TestConstructor` and the default mode.
 =====
 The default _test constructor autowire mode_ can be changed by setting the
 `spring.test.constructor.autowire.mode` JVM system property to `all`. Alternatively, the
-default mode may be set via the `SpringProperties` mechanism.
+default mode may be set via the
+https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/SpringProperties.html[`SpringProperties`]
+mechanism.
 
 As of Spring Framework 5.3, the default mode may also be configured as a
 https://junit.org/junit5/docs/current/user-guide/#running-tests-config-params[JUnit Platform configuration parameter].
@@ -1878,7 +1880,8 @@ change the default mode.
 =====
 The default _enclosing configuration inheritance mode_ is `INHERIT`, but it can be
 changed by setting the `spring.test.enclosing.configuration` JVM system property to
-`OVERRIDE`. Alternatively, the default mode may be set via the `SpringProperties`
+`OVERRIDE`. Alternatively, the default mode may be set via the
+https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/SpringProperties.html[`SpringProperties`]
 mechanism.
 =====
 
@@ -4565,8 +4568,9 @@ The size of the context cache is bounded with a default maximum size of 32. When
 maximum size is reached, a least recently used (LRU) eviction policy is used to evict and
 close stale contexts. You can configure the maximum size from the command line or a build
 script by setting a JVM system property named `spring.test.context.cache.maxSize`. As an
-alternative, you can set the same property programmatically by using the
-`SpringProperties` API.
+alternative, you can set the same property via the
+https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/SpringProperties.html[`SpringProperties`]
+mechanism.
 
 Since having a large number of application contexts loaded within a given test suite can
 cause the suite to take an unnecessarily long time to run, it is often beneficial to