nodejs/test/parallel/test-process-exit-recursive.js

'use strict';
require('../common');
const assert = require('assert');

// recursively calling .exit() should not overflow the call stack
let nexits = 0;

process.on('exit', function(code) {
  assert.strictEqual(nexits++, 0);
  assert.strictEqual(code, 1);

  // now override the exit code of 1 with 0 so that the test passes
  process.exit(0);
});

process.exit(1);
test: enable linting for tests Enable linting for the test directory. A number of changes was made so all tests conform the current rules used by lib and src directories. The only exception for tests is that unreachable (dead) code is allowed. test-fs-non-number-arguments-throw had to be excluded from the changes because of a weird issue on Windows CI. PR-URL: https://github.com/nodejs/io.js/pull/1721 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> 2015-05-19 13:00:06 +02:00			`'use strict';`
test: load common.js to test for global leaks common.js contains code that checks for variables leaking into the global namespace. Load common.js in all tests that do not intentionally leak variables. PR-URL: https://github.com/nodejs/node/pull/3095 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> 2015-09-27 15:31:36 -07:00			`require('../common');`
test: use const for all require() calls PR-URL: https://github.com/nodejs/node/pull/10550 Reviewed-By: Rich Trott <rtrott@gmail.com> 2016-12-30 18:38:06 -05:00			`const assert = require('assert');`
process: ensure that the "exit" event always has "code" given Upon "normal" exiting of Node (i.e. the event loop completes naturally), the "code" parameter was not being passed to the "exit" event listeners. Be consistent. Tests included. 2012-04-29 18:53:41 -07:00
			`// recursively calling .exit() should not overflow the call stack`
test: use eslint to fix var->const/let Manually fix issues that eslint --fix couldn't do automatically. PR-URL: https://github.com/nodejs/node/pull/10685 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io> 2017-01-08 13:19:00 +00:00			`let nexits = 0;`
process: ensure that the "exit" event always has "code" given Upon "normal" exiting of Node (i.e. the event loop completes naturally), the "code" parameter was not being passed to the "exit" event listeners. Be consistent. Tests included. 2012-04-29 18:53:41 -07:00
			`process.on('exit', function(code) {`
test: s/assert.equal/assert.strictEqual/ Use assert.strictEqual instead of assert.equal in tests, manually convert types where necessary. PR-URL: https://github.com/nodejs/node/pull/10698 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com> 2017-01-08 15:36:25 +00:00			`assert.strictEqual(nexits++, 0);`
			`assert.strictEqual(code, 1);`
process: ensure that the "exit" event always has "code" given Upon "normal" exiting of Node (i.e. the event loop completes naturally), the "code" parameter was not being passed to the "exit" event listeners. Be consistent. Tests included. 2012-04-29 18:53:41 -07:00
			`// now override the exit code of 1 with 0 so that the test passes`
process: Fix regression from a5dba82 Respect numeric string args to process.exit(code) 2013-09-06 18:23:02 -07:00			`process.exit(0);`
process: ensure that the "exit" event always has "code" given Upon "normal" exiting of Node (i.e. the event loop completes naturally), the "code" parameter was not being passed to the "exit" event listeners. Be consistent. Tests included. 2012-04-29 18:53:41 -07:00			`});`

			`process.exit(1);`