GeezerVison

Perhaps too tangentially related to this change, but since "refactor" is general, perhaps not?:

We have (at least) three test files for the beforeExit event and they are all (IMO) sub-optimally named:

• test-processs-before-exit.js
• test-beforeexit-event-exit.js
• test-beforeexit-event.js

Perhaps we can take this opportunity to rename them all to test-process-beforeExit-*?

A search for 'beforeExit' in the test directory returned 9 files. If you let me know exactly which ones you want renamed (just the three you mentioned above?), I can rename them in another commit.

@cjihrig Looking more closely at it, two of the tests are awfully similar and could/should probably be merged. I have a feeling once we start pulling on this thread, lots of other things may shake out, so, uh, yeah, never mind. :-D I'll probably try to sort it out after this lands.

(Actually, if you could just rename this test to test/parallel/test-process-beforeExit-exit.js, that would be great. I'll rename the others.)

I commented elsewhere, but it looks to me like use of camelCase in the test folder is unconventional, most of the project sticks to non-case-sensitive filenaming conventions. Wouldn't we better getting rid of the camelCase, converting to minus-seperators, the dominant convention?

I commented elsewhere, but it looks to me like use of camelCase in the test folder is unconventional, most of the project sticks to non-case-sensitive filenaming conventions. Wouldn't we better getting rid of the camelCase, converting to minus-seperators, the dominant convention?

@sam-github You make some good points here and elsewhere. The counterargument is that knowing to do that conversion is one more piece of friction. "I know I'm looking for a beforeExit test. Let's look for tests with beforeExit in the name! None? OK. Maybe it's beforeexit. Or before-exit. Or something, I guess?" I'd rather there be just one and only one name for the event/method/whatever, not different names depending on if I'm looking for a filename or not.

I don't feel that strongly enough about it to push for it, and in the absence of a champion, status quo wins out. Sadly, it's not just the 43 mixed case files to consider changing. It's also lowercase everything vs. kebab-case everything: test-fs-readfilesync-pipe-large.js or test-fs-read-file-sync-hostname.js. :-(

TL;DR: We can leave this filename as is. :-D

Let's look for tests with beforeExit in the name! None? OK. Maybe it's beforeexit. Or before-exit. Or something, I guess?

agreed, the mapping should be clear and consistent. Could be I've been burned to badly with projects that literally could not be checked out on OS X or Windows because of case changes, and yes, that was with Subversion, but my interactions with tooling on mixed case projects have been poor at times.

In this case, if there is a majority practice, I'd document it, and then we can evolve towards it.

CI: https://ci.nodejs.org/job/node-test-pull-request/5707/