Repository navigation
Reorganize Node Tests #52502
Description
What is the problem this feature will solve?
Currently, the /test folder is full of thousands, seemingly random files.
What is the feature you are proposing to solve the problem?
I propose a reorganization of this folder so that:
(A) GitHub doesn't truncate the files to first 1000 when loading in the repo
(B) The files will be easier to find
What alternatives have you considered?
No response
Activity
MoLow commentedon Apr 13, 2024
what is a suggested alternative?
I don't think this is something that makes the codebase hard since you either add a new file, or edit a file that you already know the name of, and haven't heard anyone else complain about this. however I am willing to here (or just review a PR) with suggestions
avivkeller commentedon Apr 13, 2024
I'd feel like organizing it to
/test/<...>/<subsystem>/<test>.jswould be easier. But that's not an easy task.joyeecheung commentedon Apr 13, 2024
That would make
git log test/paralell/...harder. Also/test/<...>/<subsystem>/<test>.jsisn't really too different fromtest-...-<subsystem>-test.jsand in general the tests are named in the patterntest-<module>-<api>.jsalready. They are definitely not randomly named. For example if you want to run all the http tests you could just dotools/test.py "*/*http*". And as you add more folders than you'll need to differentiate the parallel ones and the sequential ones, which isn't as clear as just putting them in theparallel/sequentialfolder.