Surfaced by #249's review: ci.yml's test job runs on ubuntu only, while the suite carries Windows-specific coverage (pathsHandlersWin32, the atomic-write crash tests whose rename semantics differ on Windows, backgroundHandlers symlink cases that skipIf themselves on win32). Those tests either never execute on the platform they exist for, or execute only in their skipped form.
The build job already runs on windows-latest, so the runner cost of adding test to the same matrix is one more job, not a new platform. Worth deciding: full suite on Windows in the matrix, or a targeted windows-only test job running the win32-relevant files if the full suite is too slow there. Either beats the current state, where a Windows-only regression in a path the suite covers would sail through CI green.
Surfaced by #249's review: ci.yml's test job runs on ubuntu only, while the suite carries Windows-specific coverage (pathsHandlersWin32, the atomic-write crash tests whose rename semantics differ on Windows, backgroundHandlers symlink cases that skipIf themselves on win32). Those tests either never execute on the platform they exist for, or execute only in their skipped form.
The build job already runs on windows-latest, so the runner cost of adding test to the same matrix is one more job, not a new platform. Worth deciding: full suite on Windows in the matrix, or a targeted windows-only test job running the win32-relevant files if the full suite is too slow there. Either beats the current state, where a Windows-only regression in a path the suite covers would sail through CI green.