Currently, there is no way to pass cliOptions in the automated tests, making it difficult to test these flags. This PR aims to solve that with the following:
Adds a test configuration object in test/lib/optionMap.ts. This allows you to specify a test file path as key, and a configuration object as the value to customize the cliOptions, comparisonArgs, and target language for that test.
If the current test language does not match that specified in optionMap, the test is skipped. This is necessary since different languages support different CLI options.
Allows you to specify an input and expected output JSON file for tests. This is necessary since some cliOptions (such as omit-empty) are expected to produce a different JSON as output in some cases. I've adopted a standard file naming for input files matching this regex: /^(.*)\.in\.(.*)$/, and output files matching this regex: /^\1\.out\.\2$/. For example myCustomTest.in.json and myCustomTest.out.json. If an input file is found with no matching output, an error is thrown with a message indicating the issue.
No changes are necessary for any existing tests, this just adds the ability to write more customizable additional tests. Unsure if there is a better way to do this, any feedback is welcome!
Currently, there is no way to pass cliOptions in the automated tests, making it difficult to test these flags. This PR aims to solve that with the following:
test/lib/optionMap.ts. This allows you to specify a test file path as key, and a configuration object as the value to customize the cliOptions, comparisonArgs, and target language for that test./^(.*)\.in\.(.*)$/, and output files matching this regex:/^\1\.out\.\2$/. For examplemyCustomTest.in.jsonandmyCustomTest.out.json. If an input file is found with no matching output, an error is thrown with a message indicating the issue.No changes are necessary for any existing tests, this just adds the ability to write more customizable additional tests. Unsure if there is a better way to do this, any feedback is welcome!