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

Port more backend tests from wradlib #72

Open
5 of 6 tasks
kmuehlbauer opened this issue Feb 5, 2023 · 1 comment
Open
5 of 6 tasks

Port more backend tests from wradlib #72

kmuehlbauer opened this issue Feb 5, 2023 · 1 comment

Comments

@kmuehlbauer
Copy link
Collaborator

kmuehlbauer commented Feb 5, 2023

  • xradar version: 0.0.10
  • Python version: 3.11
  • Operating System: Linux

Description

When porting the code for the backends from wradlib to xradar I've only implemented light testing of overall functionality. I'm currently in the process to actually use xradar from wradlib, removing duplicated code.

There are a bunch of tests still at wradlib, which are better living here.

@kmuehlbauer
Copy link
Collaborator Author

While exploring #138, #139 I've found that a lot of functionality in some backends is not test-friendly abstracted into functions/methods. Instead it needs a file to test the workflow.

Let's use this issue to keep track of wanted/needed changes.

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

No branches or pull requests

1 participant