diff --git a/junit-jupiter-api/src/main/java/org/junit/jupiter/api/Assumptions.java b/junit-jupiter-api/src/main/java/org/junit/jupiter/api/Assumptions.java
index f1ade0746475..68b0b66ac62f 100644
--- a/junit-jupiter-api/src/main/java/org/junit/jupiter/api/Assumptions.java
+++ b/junit-jupiter-api/src/main/java/org/junit/jupiter/api/Assumptions.java
@@ -27,7 +27,12 @@
  *
  * <p>In direct contrast to failed {@linkplain Assertions assertions},
  * failed assumptions do not result in a test <em>failure</em>; rather,
- * a failed assumption results in a test being <em>aborted</em>.
+ * a failed assumption results in a test being <em>aborted</em>. However,
+ * failed assertions and other exceptions thrown by tests take precedence over
+ * failed assumptions when both are thrown during the execution of a test
+ * (for example, by different lifecycle methods), regardless of the order they
+ * are thrown in. In such cases, the test will be reported as <em>failed</em>
+ * rather than <em>aborted</em>.
  *
  * <p>Assumptions are typically used whenever it does not make sense to
  * continue execution of a given test method &mdash; for example, if the