Tests: Create static inputs

[joeflack4]

Overview

Update 2024/12: We've determined that --fast-run is deterministic, and have instead tweaked that to be more thorough, and are using that instead of this. Static inputs would be nicer, but it is not so important now.

Would be nice to have alternative variations for all test input files. These should be smaller so that tests run faster. The data should also be synthetic to avoid any licensing issues.

Sub-tasks

• 1. Simple inputs: Create synthetic test inputs that have a small number of rows.
• 2. Config: Set up so that when test is run, it uses these inputs instead of what's listed in the comploinc_config.yaml
• 3. Updated inputs: Upgrade inputs for internal consistency

3. Upgrade inputs for internal consistency

Ideally, the synthetic terms and properties between the files should/would be linked so that the output makes more sense and more sensible tests can be run. What I mean by this is that the synthetic part terms created in one file should be shown in other files, synthetic LOINC terms should appear in the synthetic LOINC release, as well as the LOINC tree, etc. SNOMED-Ontology synthetic terms should be found both in synthetic SNOMED and LOINC. This might be a tall order though; so maybe could leave this requirement out for the first iteration.

[joeflack4]

Another reason to do this is that this it might be the best way to fix:

• Tests: Improve n of SNOMED outputs #116

[joeflack4]

Update 2024/12: We've determined that --fast-run is deterministic, and have instead tweaked that to be more thorough, and are using that instead of this. Static inputs would be nicer, but it is not so important now.