Stop distributing test files?

[santisoler]

Description:

Currently most of our libraries hold their test functions along with the source code. Moreover, when we distribute the code (upload to PyPI or conda-forge) we are also providing this test functions and classes, along with the test data they need. This forces each user to download a bunch of files that they are not going to ever use (see #44). Particularly Harmonica is seeing its test/data folder to growing a lot with sample grid files.

Would be better if we don't distribute the test folder inside the source code of our packages. This will lower the bandwidth and disk space required to install our packages without changing the user experience. If anyone wants to test the code, they will have to git clone the repo and run the tests, but this is how they should do so already.

Is there any reason why we would like to keep distributing those?

cc @leouieda

Apply to:

• boule
• harmonica
• pooch
• verde
• ensaio

Further instructions:

• Start by opening Pull Requests on each repository listed above.
• Optionally, we can open Issues on each repository if further discussion specific to that repository is needed.
• Mention this Issue on every Issue or Pull Request opened on each opened: Related to fatiando/community#77
• Check-off the repository on the list above once the Pull Request is merged.
• Close this issue when all items are checked-off.

We want your help!

We know that maintenance tasks are very demanding, so we don't expect a single person to tackle this issue by themselves. Any help is very welcomed, so please comment below that you want to take care of the changes on any repository and we will assign it to you.

[leouieda]

Packaging the tests lets us run the tests on the installed/packaged code like this: https://github.com/conda-forge/verde-feedstock/blob/main/recipe/meta.yaml#L39

But I'm not sure how useful that turns out to be.