From 6b9f15d9d53ceef1db1a0fa1fd3e7f38f757e88e Mon Sep 17 00:00:00 2001
From: Sam Brannen <104798+sbrannen@users.noreply.github.com>
Date: Mon, 9 Sep 2024 14:01:42 +0200
Subject: [PATCH] Delete unnecessary (and potentially misleading) comment in
 User Guide

(cherry picked from commit 1e50843c38b2b7eaf0659521b7bb792aeeeb9e13)
---
 documentation/src/docs/asciidoc/user-guide/writing-tests.adoc | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/documentation/src/docs/asciidoc/user-guide/writing-tests.adoc b/documentation/src/docs/asciidoc/user-guide/writing-tests.adoc
index 49a5d4ff3f9b..3a161bf3185f 100644
--- a/documentation/src/docs/asciidoc/user-guide/writing-tests.adoc
+++ b/documentation/src/docs/asciidoc/user-guide/writing-tests.adoc
@@ -2428,10 +2428,6 @@ lambda expression for a dynamic test, those fields will not be reset by callback
 or extensions between the execution of individual 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
-release.
-
 [[writing-tests-dynamic-tests-examples]]
 ==== Dynamic Test Examples