Add N&N entry for JDT JUnit 6 support

Fixes: #436

Author: trancexpress

news/4.38/images/JUnit6AddClasspathContainer.png

@@ -7,10 +7,44 @@ A special thanks to everyone who [contributed to JDT](acknowledgements.md#java-d
 ## Java™ XX Support 
 -->
 
-<!--
+
 ---
 ## JUnit
--->
+
+### Eclipse support for JUnit 6.0.1
+<!-- https://github.com/eclipse-jdt/eclipse.jdt/issues/147 -->
+<details>
+<summary>Contributors</summary>
+
+- [Christoph Laeubrich](https://github.com/laeubi)
+- [Ed Merks](https://github.com/merks)
+- [Hannes Wellmann](https://github.com/HannesWell)
+- [Simeon Andreev](https://github.com/trancexpress)
+</details>
+
+#### Create a new JUnit Jupiter test via **New JUnit Test Case** wizard:
+
+![New JUnit Jupiter Test Case Wizard](images/JUnit6NewTestCaseWizard.png)
+
+#### Add JUnit 6 library to the build path:
+
+New JUnit Test Case wizard offers to add it while creating a new JUnit Jupiter test:
+
+![Add JUnit 6 Container for New Test Case](images/JUnit6AddClasspathContainer.png)
+
+Quick Fix **(Ctrl+1)** proposal on `@Test`, `@TestFactory`, `@ParameterizedTest` and `@RepeatedTest` annotations:
+
+![Quick Fix Proposal JUnit 6 Container](images/JUnit6QuickFixProposal.png)
+
+Add JUnit library in Java Build Path dialog:
+
+![Build Properties Page JUnit 6 Container](images/JUnit6BuildPropertiesContainer.png)
+
+See also:
+
+[JUnit 6 Changelog](https://docs.junit.org/6.0.0/release-notes/)
+
+[JUnit 5 New & Noteworthy in Eclipse 4.8](https://eclipse.dev/eclipse/news/4.8/jdt.html#JUnit)
 
 <!--
 ---

news/4.38/images/JUnit6BuildPropertiesContainer.png

@@ -14,3 +14,20 @@ A special thanks to everyone who [contributed to PDE](acknowledgements.md#plug-i
 ---
 ## PDE Compiler 
 -->
+
+---
+## JUnit Plug-in Test Launch
+
+### JUnit 5 and JUnit 6 conflicts in Eclipse 4.38+
+
+Eclipse 4.38 supports JUnit 6 in parallel to JUnit 5. To achieve this, the platform contains both JUnit 5 and JUnit 6.
+This can result in launch configuration and runtime problems in tests,
+when a plug-in does not correctly bound the version of JUnit Jupiter (JUnit 5 and JUnit 6) bundles.
+
+The most common problem is running a JUnit 5 plug-in test launch with a `MANIFEST.MF` dependency to `junit-jupiter-api`.
+This will result in no tests executed. To resolve the problem, either specify a version bound `junit-jupiter-api;bundle-version="[5.0.0,6.0.0)"`
+or update the test launch to use JUnit 6. Other unbound dependencies to JUnit Jupiter bundles can likewise result in no executed tests.
+
+A more difficult to analyze problem is when a transitive dependency of the plug-in has an unbound dependency to JUnit Jupiter.
+The Plug-in Explorer view or the [Plug-in Dependencies](https://github.com/iloveeclipse/plugindependencies) view
+can be used to analyze unexpected dependencies to JUnit 6.