gee-community/pytest-gee

The pytest plugin for your gee package 🌍

pytest-gee's Issues

"visually" test on ee.Image

Is your feature request related to a problem? Please describe.
Some processing done in GEE side are better checked by "seeing" the image, e.g. smoothing filters, convolutions and many others. Would be like saying that a bunch of pixels have always the same values, but also being able to see the results is a plus.

Describe the solution you'd like
data_regression plugin being able to store the image and check against it. It could benefit from the new ee.data.getPixels or computePixels methods

Additional context
Test should be performed over small areas. Maybe the plugin could do some checking on this, or at least warn the user if the fetching is too large.

drop coverage as it doesn't see that methods and fixture are called in the tests

Check query before fetching data from server

Problem
Commercial user of GEE API get charged for its usage, so every time a test is triggered, it fetches data from server creating cost for the company. Also, it takes time to fetch data, so when trying to run a complete set of tests, it could take long to finish.

Solution
Save the query string into a file (write/read functionality can be found in geetools) and, when the test is triggered, first check if the query string is the same, if True then skip it, if False then fetch.

Context
The version of GEE python API could be something to consider, since the structure of the query could change from version to version, thus a version check could be implemented. The version should be stored somewhere alongside the query string, so to avoid having to modify the string and for example create a new string/dict with the version code, my proposal is to write it as part of the filename, something like: test_some_method_0-1-384.gee

Probably @tylere could have an opinion on this.

publish on conda

document a testing process

more less what we did in pyGAUL but step by step with the pytest_plugin tools.

add documentation to create new init method

At the moment we simply use the init method presetn in pyGAUL and other libs that I wrote. I cannot cover all the use cases but the community should be able to implement new ones. At least suggest it in the documentation.

Manage a folder in GEE

when launching the test the user should be able to create a tmp folder in its assets to check exportation operations. The folder and all its content will be removed at tear-down step.

Note that the name of the folder will use the hash key define at session level.