Skip to content

nested test counting is wrong #47696

Closed
Closed
nested test counting is wrong#47696
Labels
confirmed-bugIssues and PRs for confirmed bugs.test_runnerIssues and PRs related to the test runner subsystem.

Description

@MoLow
MoLow
opened on Apr 24, 2023

Version

v18.16.0, v21.0.0-pre

Platform

Darwin Moshes-MacBook-Pro.local 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar 6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000 arm64

Subsystem

test_runner

What steps will reproduce the bug?

echo "require('node:test')('1');require('node:test')('2');" > a.js 
echo "require('node:test')('3');" > b.js 
./node --test-reporter=tap --test a.js b.js

How often does it reproduce? Is there a required condition?

allways

What is the expected behavior? Why is that the expected behavior?

TAP version 13
# Subtest: 1
ok 1 - 1
  ---
  duration_ms: 0.454042
  ...
# Subtest: 2
ok 2 - 2
  ---
  duration_ms: 0.048792
  ...
# Subtest: 3
ok 3 - 3
  ---
  duration_ms: 0.4455
  ...
1..3
# tests 3
# suites 0
# pass 3
# fail 0
# cancelled 0
# skipped 0
# todo 0

each test should have its index

What do you see instead?

TAP version 13
# Subtest: 1
ok 1 - 1
  ---
  duration_ms: 0.454042
  ...
# Subtest: 2
ok 2 - 2
  ---
  duration_ms: 0.048792
  ...
# Subtest: 3
ok 2 - 3
  ---
  duration_ms: 0.4455
  ...
1..3
# tests 3
# suites 0
# pass 3
# fail 0
# cancelled 0
# skipped 0
# todo 0

tests are ok 1 ok 2 ok 3

Additional information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmed-bugIssues and PRs for confirmed bugs.test_runnerIssues and PRs related to the test runner subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions