: I'm hoping you have some thoughts here.
If I understand correctly, at some point, all of the .input files will be run against .ind scripts and validated against corresponding .output files, all as part of a test suite, presumably using command-runner.
At this point, I'm assuming the automated test suite will use file names to correlate .ind with .input/.output. So, e.g., get-system-status.ind will have get-system-status.input and get-system-status.output, and that's how the test suite will "know" which .input/.output files to run against a given .ind script.
So, then, will it possible to have multiple .input/.output pairs for one .ind script? (I hope so.) If so, how will we name them? e.g.,
Could the test suite pick that up and run it against the get-system-status.ind script? The current use case is fortigate, where we already have varying command output for the same command across multiple versions. We _could_ just jam all of this different output into a single .input file, but that could get really confusing -- especially for people coming later to the game....