Closed stscicrawford closed 5 years ago
Some example:
@stsci-hack https://innerspace.stsci.edu/display/SSR/Adding+New+Tests%3A+A+User%27s+Guide
Comments about testing workflows from #9
Also maybe mention something like "use urllib/astroquery/astropy.utils.data, not roll-your-own-downloader when remote data is required"?
One step further might even be "and use some pytest markers to indicate that these require downloading" - the astropy machinery for this is a lot easier to integrate now that it is a stand-alone and does not require the helpers.
cc @bhilbert4
Testing can cover several things:
Also mention different CI services to choose from:
@pllim I might not understand the scope of this guide, but isn't the Institute trying to limit CI tools to Jenkins (for internal projects) and Travis CI (for outside collaborative projects)?
And links to pytest
resources.And some plugins that might be useful for pytest
:
Re: limit CI tools -- but does that mean we should never test under Windows? :woman_shrugging: (this is when I slowly back away towards the door)
Also guideline for when to bundle test data with the package, and when to use "big data" solution?
I've assigned @pllim to take a first draft. After that is available, we can then iterate on it and add more material
@drdavella , want to be co-author? 😉
Sure, I'm happy to help and/or review.
@stscicrawford , is there a deadline for this...? :grimacing:
Add information about testing workflows.