Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update and Add Tests for FileSet, Collocator and SPAREICE #216

Open
10 tasks
JohnMrziglod opened this issue Aug 28, 2018 · 4 comments
Open
10 tasks

Update and Add Tests for FileSet, Collocator and SPAREICE #216

JohnMrziglod opened this issue Aug 28, 2018 · 4 comments

Comments

@JohnMrziglod
Copy link
Member

JohnMrziglod commented Aug 28, 2018

Owing to the recent development of these classes, there are just a few tests working and most of them are obsolete. Hence, they need a review and many tests must be added. This issue acts as a ToDo list for tests and will be updated in future.

FileSet and FileHandler

  • Test FileSet.align
  • Test MHS_HDF.read
  • Test AVHRR_HDF.read
  • Test CloudSat.read

Collocator, Collocations and related functions

  • Test Collocator.collocate
  • Test Collocator.collocate_filesets or Collocations.search
  • Test collapse
  • Test expand

SPAREICE

  • Test SPAREICE.retrieve
  • Test SPAREICE.retrieve_from_collocations
@JohnMrziglod
Copy link
Member Author

@olemke and @lkluft ,
I would like to test the file handler of MHS, etc. Do you know a good way of doing this? For instance, is it possible to ship an original MHS file as test case?

@olemke
Copy link
Member

olemke commented Sep 27, 2018

Since it's likely that other similar test files need to be added in the future and they're of considerable size, it is not feasible to have them inside the typhon repository itself.
After discussion with @lkluft, we came to the conclusion that we should have a separate typhon-testfiles repository which can be optionally checked out alongside typhon. If this repository is present (location could also be set by the user via an environment variable TYPHONTESTFILES) the tests that require these additional files are executed and otherwise skipped.

@JohnMrziglod
Copy link
Member Author

I like this idea of separation. But wouldn't it be more consistent to move all test scripts and files (i.e. typhon/tests) to that repository?

@olemke
Copy link
Member

olemke commented Oct 4, 2018

The tests should always be part of the main package. Tests that need larger input files to run are an exception. Usually tests don't need any input files at all. Not being able to run tests without checking out a second package would be very inconvenient.
Having them separate from the main typhon package would also require two pull requests to add code and tests. We already get complaints that doing one pull request to commit code is too much of a hassle, requiring two would be a death sentence for test contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants