Repository navigation
--test & --test-reporter & --test-reporter-destination will swallow error #52670
Copy link
Copy link
Closed
Labels
docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Description
Activity
- addedtest_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
on Apr 24, 2024 This seems like expected behavior that is only specific to the lcov reporter, and has nothing to do with the reporter destination. This is because the lcov reporter's only functionality is to report code coverage information. It might be worth updating the lcov reporter docs to specify that:
- No test results are reported by this reporter.
- This reporter should ideally be used in conjunction with another reporter.
Reacted by Alex Yang, Chemi Atlow and Moshe Atlow- addeddocIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.
on Apr 25, 2024 You're wanting to see this update in here:
?Line 503 in 7c3dce0
The tap and spec reporters will print a summary of the coverage statistics. I can take this and open a PR if that's OK?
Reacted by Alex YangThank you
@cjihrig, @himself65 can you check if my pull request it's ok about this issue #52746
is this issue this open ? can i work on it im a new guy
- linked a pull request that will close this issueCoverage reporter shallow error doc #52746
on May 15, 2024 The command to get console output AND coverage is quite long:
node --test \ --test-reporter spec --test-reporter-destination stdout \ --experimental-test-coverage --test-reporter lcov --test-reporter-destination lcov.infoThis was closed by #53523.
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Version
18,x 20.x, 22
Platform
macos
Subsystem
test_runner
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
Additional information
No response