search

stuckyb / gcdl

6 stars 2 forks source link

automated tests #29

Closed stuckyb closed 2 years ago

stuckyb commented 2 years ago

As this projects expands in complexity and scope, we really need to implement an automated testing framework for QA/QC as new code is developed.

Hedrick-ARS commented 2 years ago

I wholeheartedly agree. We have had success in our repos using the native Github actions after our previous approach went behind a paywall.

HeatherSavoy-USDA commented 2 years ago

Sure would be handy! I was thinking about that when writing out cases in #27. Would we include some example data layers in the repo to test on?

stuckyb commented 2 years ago

A basic unit testing framework was implemented in 070d9fb7c87049c and subsequent commits. Much new code added since then has (nearly) full test coverage, but much work is still needed to add tests for the remaining core classes.

stuckyb commented 2 years ago

Re: example data to test on, 649cb6caaa97164d9b added a custom, artificial dataset for testing tile management. I think that sort of approach (small, carefully crafted test data) could work well for much of what we'd need and still maintain a very small disk footprint.

HeatherSavoy-USDA commented 2 years ago

I think given the more recent closed issues related to testing (e.g. #58), this issue can be closed. Specific testing needs are being added as new issues.