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
Current implementation of unittests is becoming cumbersome:
matrix of 4 testing scripts that test:
api and developer facing code
spatial data read from a .shp and a geopandas.GeoDataFrame
While retaining the basic testing of input, once certain values have been determined to be correct limit testing. For example, if the values of calculation A are equal following a data read from a .shp and a gdf, then calculation B needs only to be performed using the data from either the .shp or gdf, not both. In this way tests will run more quickly and be less time consuming to maintain.
The text was updated successfully, but these errors were encountered:
Current implementation of
unittests
is becoming cumbersome:api
anddeveloper
facing code.shp
and ageopandas.GeoDataFrame
While retaining the basic testing of input, once certain values have been determined to be correct limit testing. For example, if the values of calculation A are equal following a data read from a
.shp
and agdf
, then calculation B needs only to be performed using the data from either the.shp
orgdf
, not both. In this way tests will run more quickly and be less time consuming to maintain.The text was updated successfully, but these errors were encountered: