A naming convention for our various kinds of json files?

[jernst]

We have all sorts of JSON files now:

• Test plans
• Constellations that can be used to create Test Plans
• Session templates that can be used to create Test Plans
• run --json-produced TestRun transcripts

I'm noticing I'm having a bit of difficulties telling from the name of the file what it might be. Particularly, I'm frequently confusing the Test plan and the result of the executed test plan. I did put a type field into the TestRun transcripts, which can help a bit but only after looking at the file, and it's not necessarily at the beginning of the file either.

Should we come up with some kind of naming convention?

[jernst]

Now have a directory hierarchy that seems to make some kind of sense. Closing for now.