Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polish contribution

Browse Source 
See: gh-456
This commit is contained in:
Sam Brannen
2019-02-22 19:19:59 +01:00
parent b4fc7b410b
commit 9f751ef914
1 changed files with 16 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
src/docs/asciidoc/testing.adoc
View File

@@ -3520,17 +3520,25 @@ Annotating a test method with `@Transactional` causes the test to be run within
transaction that is, by default, automatically rolled back after completion of the test.
If a test class is annotated with `@Transactional`, each test method within that class
hierarchy runs within a transaction. Test methods that are not annotated with
`@Transactional` (at the class or method level) are not run within a transaction.
Furthermore, tests that are annotated with `@Transactional` but have the `propagation`
type set to `NOT_SUPPORTED` are not run within a transaction.
`@Transactional` (at the class or method level) are not run within a transaction. Note
that `@Transactional` is not supported on test lifecycle methods — for example, methods
annotated with JUnit Jupiter's `@BeforeAll`, `@BeforeEach`, etc. Furthermore, tests that
are annotated with `@Transactional` but have the `propagation` type set to
`NOT_SUPPORTED` are not run within a transaction.
[TIP]
====
When using TestNG `@BeforeClass`,`@BeforeSuite` methods can not be used with the
`@Transactional` annotation, as they are considered non transactional methods by the
the spring text contetxt framework. However, you can inject a `PlatfromTransactionManager`
or a `TransactionTemplate` and use it within `@BeforeClass` method to perform a
transaction.
Method-level lifecycle methods — for example, methods annotated with JUnit Jupiter's
`@BeforeEach` or `@AfterEach` — are run within a test-managed transaction. On the other
hand, suite-level and class-level lifecycle methods — for example, methods annotated with
JUnit Jupiter's `@BeforeAll` or `@AfterAll` and methods annotated with TestNG's
`@BeforeSuite`, `@AfterSuite`, `@BeforeClass`, or `@AfterClass` — are _not_ run within a
test-managed transaction.
If you need to execute code in a suite-level or class-level lifecycle method within a
transaction, you may wish to inject a corresponding `PlatformTransactionManager` into
your test class and then use that with a `TransactionTemplate` for programmatic
transaction management.
====
Note that <<testcontext-support-classes-junit4,