describe and Deno.test() don't mix

[dandv]

Describe the bug

Thinking test is an eventually alias for Deno.test(), I didn't pay much attention when I left Deno.test()s inside a describe during a refactoring. But the result is that the describe succeeds even if a Deno.test() fails.

Steps to Reproduce

main_test.ts:

import { describe } from '@std/testing/bdd';
import { assertEquals } from "@std/assert";

describe('addition', () => {
  Deno.test(function addTest1() {
    assertEquals(2 + 3, 6);
  });

  Deno.test(function addTest2() {
    assertEquals(2 + 2, 4);
  });
});

$ deno test
Check file:///home/dandv/deno-bugs/main_test.ts
running 3 tests from ./main_test.ts
addTest1 ... FAILED (7ms)
addTest2 ... ok (0ms)
addition ... ok (0ms)

 ERRORS

addTest1 => ./main_test.ts:5:8
error: AssertionError: Values are not equal.


    [Diff] Actual / Expected


-   5
+   6

  throw new AssertionError(message);
        ^
    at assertEquals (https://jsr.io/@std/assert/1.0.10/equals.ts:64:9)
    at addTest1 (file:///home/dandv/deno-bugs/main_test.ts:6:5)

 FAILURES

addTest1 => ./main_test.ts:5:8

FAILED | 2 passed | 1 failed (14ms)

error: Test failed

Expected behavior

Same as if replacing Deno.test with test. Now,

• running 3 tests from ./main_test.ts is incorrect
• addition should not be ok
• FAILED | 2 passed | 1 failed - incorrect

Environment

• OS: Fedora Linux 38
• deno version: 2.1.4
• std version: @std/testing@^1.0.9

[kt3k]

These 2 sets of test runners are not supposed to work together in nested way like the above. Please use either Deno.test or describe at a time. (The mixed usage with non nested way should be fine though)