Skip to content

Tests for node test#1205

Open
rowanmanning wants to merge 2 commits intomainfrom
tests-for-node-test
Open

Tests for node test#1205
rowanmanning wants to merge 2 commits intomainfrom
tests-for-node-test

Conversation

@rowanmanning
Copy link
Copy Markdown
Member

Description

This adds in some very basic tests for the node-test plugin, I'd like to build up this test suite so I can think about switching to running tests via the command-line interface - this is required if we want to work with Node.js native test coverage and module mocks.

Checklist:

  • My branch has been rebased onto the latest commit on main (don't merge main into your branch)
  • My commit messages are conventional commits, for example: feat(circleci): add support for nightly workflows, fix: set Heroku app name for staging apps too

@rowanmanning rowanmanning requested a review from a team as a code owner March 20, 2026 15:52
@rowanmanning rowanmanning force-pushed the tests-for-node-test branch 2 times, most recently from 2152d4d to cb7652e Compare March 23, 2026 10:10
This caused an interesting issue with writing tests for this plugin,
it's fine if the `cwd` is _actually_ the `cwd` because `glob` returns
file paths relative to that. However, in the tests when we're
overriding the `cwd` to access fixture files, the relative paths don't
work because it assumes the files are relative to wherever Jest is
running from.

Anyway it shouldn't impact anyone running this normally, just blocks me
from writing tests.
This adds in some very basic tests for the node-test plugin, I'd like to
build up this test suite so I can think about switching to running tests
via the command-line interface - this is required if we want to work
with Node.js native test coverage and module mocks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant