Title: Some way of not displaying skipped or filtered tests in the spec test reporter · Issue #51383 · nodejs/node · GitHub
Open Graph Title: Some way of not displaying skipped or filtered tests in the spec test reporter · Issue #51383 · nodejs/node
X Title: Some way of not displaying skipped or filtered tests in the spec test reporter · Issue #51383 · nodejs/node
Description: What is the problem this feature will solve? In jsdom, we have 4187 tests. Sometimes I would like to run only a few of them, so I experimented with --test-name-pattern="dom/events" to only run tests under my dom/events suite. The result ...
Open Graph Description: What is the problem this feature will solve? In jsdom, we have 4187 tests. Sometimes I would like to run only a few of them, so I experimented with --test-name-pattern="dom/events" to only run test...
X Description: What is the problem this feature will solve? In jsdom, we have 4187 tests. Sometimes I would like to run only a few of them, so I experimented with --test-name-pattern="dom/events" to onl...
Opengraph URL: https://github.com/nodejs/node/issues/51383
X: @github
Domain: github.com
IPv4 address: 140.82.114.4
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Some way of not displaying skipped or filtered tests in the spec test reporter","articleBody":"### What is the problem this feature will solve?\n\nIn jsdom, we have 4187 tests. Sometimes I would like to run only a few of them, so I experimented with `--test-name-pattern=\"dom/events\"` to only run tests under my `dom/events` suite.\r\n\r\nThe result was that I saw 4100+ lines of skipped tests, within which there was somewhere buried ~50 lines of passing tests. This was not a great experience.\r\n\r\nCompare this with Mocha, where using `--fgrep=\"dom/events\"` only reports tests that match the pattern.\n\n### What is the feature you are proposing to solve the problem?\n\nI see basically two ways to solve this:\r\n\r\n- Treat filtered-out tests differently from skipped tests. For example, the totals displayed at the bottom of the test report could exclude filtered-out tests entirely. (This is how Mocha behaves.)\r\n\r\n- Provide some way of not displaying skipped tests when using the spec reporter. E.g., `--test-show-skipped=false` or something.\r\n\r\nThe former would be better for me, because sometimes I actually have tests marked as long-term skipped, and I'd like to see those even when I'm filtering. E.g. if I have 50 `dom/events` tests, of which 3 are skipped, running with `--test-name-pattern=\"dom/events\"` would ideally show 47 passes and 3 skipped. If we filtered away all skipped tests, then it would show only the 47 passes.\r\n\r\nThe latter would probably be easier to implement, and fit better with how the test runner currently works.\n\n### What alternatives have you considered?\n\nI could write my own reporter, I guess.","author":{"url":"https://github.com/domenic","@type":"Person","name":"domenic"},"datePublished":"2024-01-05T14:02:45Z","url":"https://github.com/nodejs/node/issues/51383"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:7964636f-d71d-9b1c-0622-aa7d6dd9c07f |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A6DC:2B8145:27BECE:323C63:6B033FE0 |
| html-safe-nonce | 647bd93c94f0cd0873d3e0f56c59b3c6640637ebb8bf483222aff63ac3267541 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBNkRDOjJCODE0NToyN0JFQ0U6MzIzQzYzOjZCMDMzRkUwIiwidmlzaXRvcl9pZCI6IjMzNjc5MDEwNTA3OTAxNjY0OTYiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 2935cad973c7433baee26c04a62b2255bb621b091f0eeeadcdf9d03a05ee41e8 |
| hovercard-subject-tag | issue:2067403781 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/51383/issue_layout |
| twitter:image | https://opengraph.githubassets.com/fb888e9a9a834e9ba879abd9a661d5e75f89693ebda22710a021a401dc985367/nodejs/node/issues/51383 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/fb888e9a9a834e9ba879abd9a661d5e75f89693ebda22710a021a401dc985367/nodejs/node/issues/51383 |
| og:image:alt | What is the problem this feature will solve? In jsdom, we have 4187 tests. Sometimes I would like to run only a few of them, so I experimented with --test-name-pattern="dom/events" to only run test... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | domenic |
| hostname | github.com |
| expected-hostname | github.com |
| None | 87e774ee7c6b3bee0490394e4d3e57ec9dbc956f74b87ea685dc8996c1676456 |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 423dbb54c5e7bfecc838eb387c1435eb3d0e760d |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
| Server | github.com |
| Content-Type | text/html; charset=utf-8 |
| Cache-Control | max-age=0, private, must-revalidate |
Viewport: width=device-width