File naming and hierarchy convention
Motivation
Looking at the existing PRs people seem to have different ideas for how to structure and name their test files. Unifying this would make the test suite a bit easier to read and understand.
Technical constraints
The tests need to be in the subfolder for their corresponding phase, but the names of the file and the subfolder can apparently be chosen arbitrarily:
The test cases must have unique names (in each mode folder) and can also be placed into sub folders
Ideas
- Top-Level subfolders for valid/invalid programs
- Group tests by the subsystem they try to exploit (not really relevant for the lexer, but e.g.
parser/expressions
orparser/declarations
, ...). - Use
-
instead of camel case - lowercase everything
- <here be dragons or whatever else you suggest>