Skip to content
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

Make sure extensions include tests where files are read purely on autogenerated classes #18

Open
rly opened this issue Apr 8, 2021 · 1 comment

Comments

@rly
Copy link
Contributor

rly commented Apr 8, 2021

TODO: encourage / ensure extensions include tests where files are read purely on autogenerated classes

@oruebel
Copy link
Contributor

oruebel commented Apr 8, 2021

I think an alternative approach may be that we could require that an extension include a standard test-case to generate an example HDF5 file for the extension. We could include the outline for that test as part of the extension template so that the extension developer only needs to add the code to populate the NWBFile. Once we have a way to automatically generate an example HDF5 file for an extension, we should be able to add our own set of standard tests to: 1) run validation for the file, 2) read the file with autogenerated classes only, 3) read the file with the extension installed etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants