test: rename regression tests with descriptive file names

test/parallel/test-regress-GH-3238.js → test/parallel/test-cluster-kill-disconnect.js

@@ -1,5 +1,10 @@
 'use strict';
 const common = require('../common');
+
+// Check that cluster works perfectly for both `kill` and `disconnect` cases.
+// Also take into account that the `disconnect` event may be received after the
+// `exit` event.
+
 const assert = require('assert');
 const cluster = require('cluster');
 

test/parallel/test-regress-GH-2245.js → test/parallel/test-eval-strict-referenceerror.js

@@ -1,12 +1,11 @@
 /* eslint-disable strict */
 require('../common');
-const assert = require('assert');
 
-/*
-In Node.js 0.10, a bug existed that caused strict functions to not capture
-their environment when evaluated. When run in 0.10 `test()` fails with a
-`ReferenceError`. See https://github.com/nodejs/node/issues/2245 for details.
-*/
+// In Node.js 0.10, a bug existed that caused strict functions to not capture
+// their environment when evaluated. When run in 0.10 `test()` fails with a
+// `ReferenceError`. See https://github.com/nodejs/node/issues/2245 for details.
+
+const assert = require('assert');
 
 function test() {
 

test/parallel/test-regress-GH-3739.js → test/parallel/test-fs-existssync-false.js

@@ -1,12 +1,15 @@
 'use strict';
-
 const common = require('../common');
+const tmpdir = require('../common/tmpdir');
+
+// This test ensures that fs.existsSync doesn't incorrectly return false
+// (especially on Windows)
+// https://github.com/nodejs/node-v0.x-archive/issues/3739
+
 const assert = require('assert');
 const fs = require('fs');
 const path = require('path');
 
-const tmpdir = require('../common/tmpdir');
-
 let dir = path.resolve(tmpdir.path);
 
 // Make sure that the tmp directory is clean

test/parallel/test-regress-GH-3542.js → test/parallel/test-fs-readfilesync-enoent.js

@@ -1,13 +1,19 @@
 'use strict';
 const common = require('../common');
+
+// This test ensures fs.realpathSync works on properly on Windows without
+// throwing ENOENT when the path involves a fileserver
+// https://github.com/nodejs/node-v0.x-archive/issues/3542
+
 // This test is only relevant on Windows.
-if (!common.isWindows)
-  common.skip('Windows specific test.');
 
 const assert = require('assert');
 const fs = require('fs');
 const path = require('path');
 
+if (!common.isWindows)
+  common.skip('Windows specific test.');
+
 function test(p) {
   const result = fs.realpathSync(p);
   assert.strictEqual(result.toLowerCase(), path.resolve(p).toLowerCase());

test/parallel/test-regress-GH-1531.js → test/parallel/test-http-request-agent.js

@@ -1,5 +1,6 @@
 'use strict';
 const common = require('../common');
+const fixtures = require('../common/fixtures');
 
 // This test ensures that a http request callback is called
 // when the agent option is set
@@ -8,8 +9,6 @@ const common = require('../common');
 if (!common.hasCrypto)
   common.skip('missing crypto');
 
-const fixtures = require('../common/fixtures');
-
 const https = require('https');
 
 const options = {

test/parallel/test-regress-GH-4256.js → test/parallel/test-process-domain-segfault.js

@@ -21,6 +21,11 @@
 
 'use strict';
 require('../common');
+
+// This test ensures that setting `process.domain` to `null` does not result in
+// node crashing with a segfault
+// https://github.com/nodejs/node-v0.x-archive/issues/4256
+
 process.domain = null;
 setTimeout(function() {
   console.log('this console.log statement should not make node crash');