We'd like to make a few modifications to the SRI Testing harness to facilitate agile "Smoke Tests" of the Translator system. Here is a set of features that may contribute to this goal:
[ ] add option to suppress biolink validation;
[ ] use ad hoc file of test edges (rather than a file from KP test_data_location);
[ ] Add additional “expected results” (expected nodes? Expected edges?) in the JSON test data for a given edge (possibly both positive (desired) and negative (undesirable) results) including notion that some ARA is not expected to return a given result (node? edge?)
[ ] be able to add extra unit test(s) for added functionality (Chris B. idea, related to ‘expected results’)
[ ] add functionality to run the test cases through the ARS, rather than just KP or ARA
[ ] adapt SRI Testing UI to support the above change in scope
[ ] add scripting support and guidelines for cronjob management and notifications for batch running of the testing harness to achieve SRI Testing-Lite use cases.
We'd like to make a few modifications to the SRI Testing harness to facilitate agile "Smoke Tests" of the Translator system. Here is a set of features that may contribute to this goal:
cronjobmanagement and notifications for batch running of the testing harness to achieve SRI Testing-Lite use cases.