Regression testing
dlevitas opened this issue · comments
As an active project, ezBIDS has been going through new enhancements and bug fixes. To better ensure that these updates do not inadvertently cause old bugs to reemerge, we'll need to incorporate regression testings before pushing changes. My thought is that regression testing should be for the analyzer, as it is the last automated step before users begin making edits/modifications on the UI. Given the plethora of datasets provided to us, we can test for different known edge cases to ensure that we improve coverage with each update.
Not sure if Travis CI would be appropriate, but I've heard good things.
Great idea. Yes, I like Travis CI as well. We will need to setup a various "scenarios" under ./test directory (probably just the list file and various sidecard .json that analyzer uses to analyze structure. We could also blank out some .nii.gz so we can push it as part of github without the actual image inside?)
We could also blank out some .nii.gz so we can push it as part of github without the actual image inside?)
That makes sense; however, the analyzer reads the NIfTI file to generate the PNG thumbnail. "Blanking" the file might cause an issue there. But otherwise, I like this approach
That's my hope, but I'll check