Are you asking whether every test should be in its own file? That doesn't seem like a reasonable layout. Grouping tests together into small collections is useful for organizing.

Are you asking whether every test should be in its own file?

💭 I suggest to make test case objects (like the following) usable as separate files.

• schema
• test data
• test result expectation

That doesn't seem like a reasonable layout.

I dare to present additional software development ideas.

Grouping tests together into small collections is useful for organizing.

Such information is generally fine.

💭 I propose to increase the data access granularity for involved items.

This isn't a change the suite is going to make. We may at some point tweak the layout a bit, but if you really want such a thing it's somewhat trivial to flatten the suite into individual files with some simple programming, it's just a JSON array.

💭 Can any data processing approaches benefit from the possibility to make schemas and test data better separately accessible?

Possibly! Feel free to make such a thing into a tool. The suite can already perform the opposite operation, turning itself into a single file containing all cases, by running bin/jsonschema_suite flatten.