Parser tests: test-per-file, or test-per-structure?

[jbouwman]

A commit a few months back added checks for the contents of parse error condition messages
dc4669d and doubled the number of files present in tests/parser-test-files/bad-files. There are a number of new checks I would like to add for package forms, so I wonder if keeping these test-per-file is maintainable.

Could these parser tests be grouped by functional role? For example, offhand, with section delimiters:

parse-package.tests

====
Package name type 
----
(package 1)
----
error: ...
====
Package empty
----
... and so on

Does anyone know of a good model for doing something like this?

[jbouwman]

Something like this was implemented recently, documented here:

https://github.com/coalton-lang/coalton/blob/975b0936475c380316174a7f34650a209952c9b4/tests/parser-test-files/README.md