Skip to content

Commit 5d214c2

Browse files
committed
Polishing
1 parent 6d710d4 commit 5d214c2

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

framework-docs/modules/ROOT/pages/testing/testcontext-framework/application-events.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
= Application Events
33

44
The TestContext framework provides support for recording
5-
xref:core/beans/context-introduction.adoc#context-functionality-events[application events] published in the
6-
`ApplicationContext` so that assertions can be performed against those events within
7-
tests. All events published during the execution of a single test are made available via
8-
the `ApplicationEvents` API which allows you to process the events as a
5+
xref:core/beans/context-introduction.adoc#context-functionality-events[application events]
6+
published in the `ApplicationContext` so that assertions can be performed against those
7+
events within tests. All events published during the execution of a single test are made
8+
available via the `ApplicationEvents` API which allows you to process the events as a
99
`java.util.Stream`.
1010

1111
To use `ApplicationEvents` in your tests, do the following.
@@ -24,8 +24,8 @@ To use `ApplicationEvents` in your tests, do the following.
2424
to an `@Autowired` field in the test class.
2525

2626
The following test class uses the `SpringExtension` for JUnit Jupiter and
27-
{assertj-docs}[AssertJ] to assert the types of application events
28-
published while invoking a method in a Spring-managed component:
27+
{assertj-docs}[AssertJ] to assert the types of application events published while
28+
invoking a method in a Spring-managed component:
2929

3030
// Don't use "quotes" in the "subs" section because of the asterisks in /* ... */
3131
[tabs]

0 commit comments

Comments
 (0)