Skip to content

test: add test-fs-writeFileSync-invalid-windows#28569

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Trott merged 1 commit into from
Jul 11, 2019
Merged

test: add test-fs-writeFileSync-invalid-windows #28569

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions test/known_issues/test-fs-writeFileSync-invalid-windows.js
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
'use strict';

constcommon=require('../common');

// Test that using an invalid file name with writeFileSync() on Windows returns
// EINVAL. With libuv 1.x, it returns ENOTFOUND. This should be fixed when we
// update to libuv 2.x.
//
// Refs: https://github.com/nodejs/node/issues/8987

constassert=require('assert');
constfs=require('fs');

if(!common.isWindows){
// Change to `common.skip()` when the test is moved out of `known_issues`.
assert.fail('Windows-only test');
}

assert.throws(()=>{
fs.writeFileSync('fhqwhgads??','come on');
},{code: 'EINVAL'});