Fix titles for Java tabs in Testing chapter of reference manual

This commit is contained in:
Sam Brannen 2024-08-30 17:13:14 +02:00
parent 72f912549d
commit ba64d0fae6
3 changed files with 11 additions and 6 deletions

View File

@ -20,7 +20,7 @@ managed per test method by the `ServletTestExecutionListener`.
[tabs]
======
Injecting mocks::
Java::
+
[source,java,indent=0,subs="verbatim,quotes",role="primary"]
----

View File

@ -29,9 +29,10 @@ The remaining examples in this section show some of the various configuration op
loading a `WebApplicationContext`. The following example shows the TestContext
framework's support for convention over configuration:
.Conventions
[tabs]
======
Conventions::
Java::
+
[source,java,indent=0,subs="verbatim,quotes",role="primary"]
----
@ -76,9 +77,10 @@ as the `WacTests` class or static nested `@Configuration` classes).
The following example shows how to explicitly declare a resource base path with
`@WebAppConfiguration` and an XML resource location with `@ContextConfiguration`:
.Default resource semantics
[tabs]
======
Default resource semantics::
Java::
+
[source,java,indent=0,subs="verbatim,quotes",role="primary"]
----
@ -118,9 +120,10 @@ whereas `@ContextConfiguration` resource locations are classpath based.
The following example shows that we can override the default resource semantics for both
annotations by specifying a Spring resource prefix:
.Explicit resource semantics
[tabs]
======
Explicit resource semantics::
Java::
+
[source,java,indent=0,subs="verbatim,quotes",role="primary"]
----

View File

@ -47,9 +47,10 @@ the provided `MockHttpServletRequest`. When the `loginUser()` method is invoked
set parameters). We can then perform assertions against the results based on the known
inputs for the username and password. The following listing shows how to do so:
.Request-scoped bean test
[tabs]
======
Request-scoped bean test::
Java::
+
[source,java,indent=0,subs="verbatim,quotes",role="primary"]
----
@ -124,9 +125,10 @@ the user service has access to the session-scoped `userPreferences` for the curr
`MockHttpSession`, and we can perform assertions against the results based on the
configured theme. The following example shows how to do so:
.Session-scoped bean test
[tabs]
======
Session-scoped bean test::
Java::
+
[source,java,indent=0,subs="verbatim,quotes",role="primary"]
----