From f59d734b8709482727b9308c4407e4f56aa6f61f Mon Sep 17 00:00:00 2001 From: James Roper Date: Thu, 22 Jun 2017 17:32:42 +1000 Subject: [PATCH] Remove experimental warning from testForkedParallel The `testForkedParallel` feature is almost 4 years old, and in the time that it has existed, there has never been a confirmed bug report against it. It shouldn't be considered experimental anymore. --- src/reference/02-DetailTopics/02-Configuration/14-Testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/reference/02-DetailTopics/02-Configuration/14-Testing.md b/src/reference/02-DetailTopics/02-Configuration/14-Testing.md index b41c059db..036d0915d 100644 --- a/src/reference/02-DetailTopics/02-Configuration/14-Testing.md +++ b/src/reference/02-DetailTopics/02-Configuration/14-Testing.md @@ -223,8 +223,8 @@ forked JVMs allowed to run at the same time by setting the limit on actions cannot be provided with the actual test class loader when a group is forked. -In addition, forked tests can optionally be run in parallel. This feature -is still considered experimental, and may be enabled with the following setting : +In addition, forked tests can optionally be run in parallel within the +forked JVM(s), using the following setting: ```scala testForkedParallel in Test := true