You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We expect more and more pipelines to include custom scripts (e.g. transforming CSV files, reading .shp or .nc files, scraping websites, and so on) and we need to start requiring contributors to write unit tests for them.
This will help minimize issues during internal deployment (to the Public Datasets Program) that we (Googlers) could've caught further upstream.
Some items to consider are
Where should contributors place the test files,
The unit testing conventions or guides they need to follow
Updating the README for unit testing requirements
Adding all the unit tests as part of GitHub Actions
Checklist
I created this issue in accordance with the Code of Conduct.
This issue is appropriately labeled.
The text was updated successfully, but these errors were encountered:
Description
We expect more and more pipelines to include custom scripts (e.g. transforming CSV files, reading
.shp
or.nc
files, scraping websites, and so on) and we need to start requiring contributors to write unit tests for them.This will help minimize issues during internal deployment (to the Public Datasets Program) that we (Googlers) could've caught further upstream.
Some items to consider are
Checklist
The text was updated successfully, but these errors were encountered: