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

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

// calling .exit() from within "exit" should not overflow the call stack
var nexits = 0;

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

// "exit" should be emitted unprovoked
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: remove unnecessary assignments common.js needs to be loaded in all tests so that there is checking for variable leaks and possibly other things. However, it does not need to be assigned to a variable if nothing in common.js is referred to elsewhere in the test. PR-URL: https://github.com/nodejs/node/pull/4408 Reviewed-By: James M Snell <jasnell@gmail.com> 2015-12-23 16:02:12 -08:00			`require('../common');`
process: fix stack overflow when recursively calling process.exit() 2011-12-05 22:42:05 +01:00			`var 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			`// calling .exit() from within "exit" should not overflow the call stack`
process: fix stack overflow when recursively calling process.exit() 2011-12-05 22:42:05 +01:00			`var 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) {`
process: fix stack overflow when recursively calling process.exit() 2011-12-05 22:42:05 +01:00			`assert.equal(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			`assert.equal(code, 0);`
process: fix stack overflow when recursively calling process.exit() 2011-12-05 22:42:05 +01:00			`process.exit();`
			`});`

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			`// "exit" should be emitted unprovoked`