Document dynamic test lifecycle in the User Guide

Closes: #374

Author: sbrannen

documentation/src/docs/asciidoc/writing-tests.adoc

@@ -302,12 +302,15 @@ A `DynamicTest` is a test case generated at runtime.
 It is composed of a _display name_ and an `Executable`. `Executable` is a `@FunctionalInterface`
 which means that the implementations of dynamic tests can be provided as _lambda expressions_
 or _method references_.
-Note that the execution lifecycle of dynamic tests is quite different than it is for standard `@Test` cases.
-Specifically, `@BeforeEach` and `@AfterEach` methods and their corresponding extension callbacks
-are not executed for dynamic tests.
-The execution of those callbacks would not be useful in most dynamic testing scenarios
-since variables used in lambdas are bound to instance variables at execution time of the factory method
-rather than execution time of the lambda itself.
+
+.Dynamic Test Lifecycle
+WARNING: The execution lifecycle of a dynamic test is quite different than it is for a
+standard `@Test` case. Specifically, there are not any lifecycle callbacks for dynamic
+tests. This means that `@BeforeEach` and `@AfterEach` methods and their corresponding
+extension callbacks are not executed for dynamic tests. In other words, if you access
+fields from the test instance within a lambda expression for a dynamic test, those fields
+will not be reset by callback methods or extensions between the execution of dynamic
+tests generated by the same `@TestFactory` method.
 
 As of JUnit Jupiter {jupiter-version}, dynamic tests must always be created by factory
 methods; however, this might be complemented by a registration facility in a later