-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression testing #34
Comments
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?) |
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 |
Wouldn't it just create a blank(all black) thumbnail? Would that be an
issue?
…On Fri, Sep 10, 2021 at 12:03 PM Dan Levitas ***@***.***> wrote:
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.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHBR6BMIWRDWH5GT5OPI4DUBIT47ANCNFSM5DZTDSRA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
That's my hope, but I'll check |
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.
The text was updated successfully, but these errors were encountered: