Tyler Kiley • over 9 years ago
Definition of Compatibility
The "Criteria for Evaluation of Open Source Compatibility" update contains the following paragraphs:
This condition is verified by OSEHRA utilizing a set of contestant-supplied automated software scripts that are run as “tests” against both the unmodified version of open source VistA, and against the combination of the new component integrated with open source VistA. The new component will be called “compatible with open source VistA” if the set of tests produces the same results before and after the integration.
For details on the Use Cases that contestants will have to demonstrate via automated scripts, please refer to the document “TCMS – Step 1 Test Cases”
From these paragraphs, it looks like we are supposed to design automated scripts that showcase and test the new functionality of our scheduling module, but the tests must produce the same results when run against unmodified VistA as when run against VistA with our new module.
The contest requirements seem to indicate that the test scripts should definitely be testing the new functionality we create in our submission to the contest, so by definition they require functionality that is not present in unmodified vista. In that case, I would expect our test scripts to fail (that is, produce different results) against unmodified vista; unfortunately, from the definition of compatibility above, it appears that if our automated tests for our new module do not run successfully on unmodified vista, we will fail the contest.
Can we get some clarification on this issue?
Comments are closed.