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

Move grib tests from iris into iris-grib #3476

Closed
9 of 10 tasks
lbdreyer opened this issue Oct 22, 2019 · 4 comments
Closed
9 of 10 tasks

Move grib tests from iris into iris-grib #3476

lbdreyer opened this issue Oct 22, 2019 · 4 comments

Comments

@lbdreyer
Copy link
Member

lbdreyer commented Oct 22, 2019

Currently, there are some tests in iris that test grib handling but would preferably live in iris-grib. For instance #3469 has skipped 3 tests that fail due to needing changes in iris-grib that have not yet been released.

@lbdreyer
Copy link
Member Author

Related issues: #2860 #3477 #3375

@lbdreyer
Copy link
Member Author

@pp-mo we could use this to track who is working on what

@pp-mo
Copy link
Member

pp-mo commented Feb 19, 2020

LINKS + notes (WIP editing as I go)

  • tests/__init__.py: move TestGribMessage class (do this last!)
    • Iris usage:
      • tests/integration/grib2/test_grib2 : TestPDT11 TestGDT5
      • tests/test_grib_save : TestLoadSave
  • tests/system_test.py system_test_grib_patch
    • Don't understand scope of this : where is the magic "patch" this is testing, is it just ancient + obsolete ?? -- see Remove obsolete test. #3662
  • tests/test_grib_load_translations.py
  • tests/test_grib_save.py
    • Notes:
      • uses "iris.tests.TestGribMessage".
      • TestLoadSave look ok to me
        • some load, some save, possibly better to re-organise ?
      • TestCubeSave
        • some ancient stuff in here
  • tests/test_grib_save_rules.py
    • Notes: three distinct components (testcase classes) in this testfile
      • Test_set_fixed_surfaces :
        • seems to belong in `iris_grib.tests.unit.save_rules.test_set_fixed_surfaces'
        • doesn't work in the same way : checks calls to mock(gribapi.grib_set), whereas iris-grib code checks content on an actual message. Prefer the existing way in iris-grib, may attempt to translate these. WIP
      • Test_phenomenon
        • seems to be replicating iris_grib.tests.unit.save_rules.test_set_discipline_and_parameter. ?Discard -- WIP
      • Test_type_of_statistical_processing
        • seems to belong in iris_grib.tests.unit.save_rules.test_statistical_cell_method.
          That isn't very cleam and neither is the save code itself, as not all templates go through statistical_method_code which they probably should do. Cases here are for 'minimum' + 'maximum' codes, neither of which are in existing tests. Could improve all this ? WIP
  • tests/test_uri_callback.py test_grib_callback
  • tests/integration/test_grib2.py @lbdreyer ...
  • tests/integration/test_grib_load.py
  • tests/integration/test_pickle.py TestGribMessage
  • tests/integration/format_interop/: leave for now?

@pp-mo
Copy link
Member

pp-mo commented Feb 25, 2020

All dealt with, delivered in release v0.15.1

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

No branches or pull requests

2 participants