Closed matthiaskoenig closed 6 years ago
It worries me a bit is that we now have a lot of redundant files in this repository that may be changed, maintained, and updated elsewhere, leading to a divergence over time.
What do others think? Wouldn't it be better to include a script that obtains SED-ML files etc. from the original location? We could then make sure that developers of SBSCL keep their individual copies outside of this repo?
For junit tests, it is better to be sure that the data will not change. We don't want to have the updates or changes or losing some file if location change. If you can target a specific version that we are sure will not change or be unavailable at some point that might be fine.
I think in case of the SED-ML files it is okay to put them in the repository. In total all the files are only <1MB. If this is getting too big, we can first put the files in omex archives, as a second would be to load them analoque to the BiGG and sbml-test-case files. But for now, I don't think the files are a problem.
This adds L1V2 test cases in the
/src/test/resources/sedml/L1V2
folder.