GitHub-Spring
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Polish context caching section

pull/35204/head
Sam Brannen 5 months ago
parent
4107ddc5e2
commit
f3757cedb9
1 changed files with 9 additions and 8 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 17
      framework-docs/modules/ROOT/pages/testing/testcontext-framework/ctx-management/caching.adoc

17
framework-docs/modules/ROOT/pages/testing/testcontext-framework/ctx-management/caching.adoc
Unescape View File

@ -31,10 +31,10 @@ under a key that is based solely on those locations. So, if `TestClassB` also de
`{"app-config.xml", "test-config.xml"}` for its locations (either explicitly or `{"app-config.xml", "test-config.xml"}` for its locations (either explicitly or
implicitly through inheritance) but does not define `@WebAppConfiguration`, a different implicitly through inheritance) but does not define `@WebAppConfiguration`, a different
`ContextLoader`, different active profiles, different context initializers, different `ContextLoader`, different active profiles, different context initializers, different
test property sources, or a different parent context, then the same `ApplicationContext` context customizers, different test or dynamic property sources, or a different parent
is shared by both test classes. This means that the setup cost for loading an application context, then the same `ApplicationContext` is shared by both test classes. This means
context is incurred only once (per test suite), and subsequent test execution is much that the setup cost for loading an application context is incurred only once (per test
faster. suite), and subsequent test execution is much faster.
.Test suites and forked processes .Test suites and forked processes
[NOTE] [NOTE]
@ -71,10 +71,11 @@ the underlying context cache, you can set the log level for the
In the unlikely case that a test corrupts the application context and requires reloading In the unlikely case that a test corrupts the application context and requires reloading
(for example, by modifying a bean definition or the state of an application object), you (for example, by modifying a bean definition or the state of an application object), you
can annotate your test class or test method with `@DirtiesContext` (see the discussion of can annotate your test class or test method with `@DirtiesContext` (see the discussion of
`@DirtiesContext` in xref:testing/annotations/integration-spring/annotation-dirtiescontext.adoc[Spring Testing Annotations] `@DirtiesContext` in
). This instructs Spring to remove the context from the cache and rebuild xref:testing/annotations/integration-spring/annotation-dirtiescontext.adoc[Spring Testing Annotations]).
the application context before running the next test that requires the same application This instructs Spring to remove the context from the cache and rebuild the application
context. Note that support for the `@DirtiesContext` annotation is provided by the context before running the next test that requires the same application context. Note
that support for the `@DirtiesContext` annotation is provided by the
`DirtiesContextBeforeModesTestExecutionListener` and the `DirtiesContextBeforeModesTestExecutionListener` and the
`DirtiesContextTestExecutionListener`, which are enabled by default. `DirtiesContextTestExecutionListener`, which are enabled by default.

Write Preview
Loading…
Cancel
Save