Added fixtures to conftest.py to resolve ongoing test suite failures:
default_cache: $CRDS_PATH or /tmp/crds-cache-default-test
hst_default_cache_state, jwst_default_cache_state: these use the new default_cache fixture to point directly to crds-cache-default-test, in addition to explicitly setting mode='auto', url, and observatory. Some tests were failing because they relied on the crds_shared_group_cache fixture which returns the CRDS built-in config.get_crds_path(). The path returned is not always what the test expects it to be and in many cases was incorrect (e.g. crds-cache-test or 'data/'.
Note: ultimately we may want to move remaining tests away from using the 'crds_shared_group_cache' altogether - I elected not to do that for now because the majority of tests using it were fine and I'd rather not break something that didn't need fixing.
Decorated tests with observatory-based markers according to the test configuration and/or data being used in the test. For tests that don't use an observatory-based test configuration, the marker is "multimission". The primary intention here is to aid in troubleshooting setup/teardown problems. E.g. a test with an "hst" marker might be a mission-agnostic feature of CRDS, but it explicitly relies on the hst server, hst test data, etc.
added CRDS_PATH and CRDS_TESTING_CACHE to github actions ci.yml env
CCD-1434:
Added metrics_logger decorator to Roman tests delivered with older builds (test_certify.py)
CCD-1438:
hst_default_cache_state,jwst_default_cache_state: these use the newdefault_cachefixture to point directly tocrds-cache-default-test, in addition to explicitly setting mode='auto', url, and observatory. Some tests were failing because they relied on thecrds_shared_group_cachefixture which returns the CRDS built-inconfig.get_crds_path(). The path returned is not always what the test expects it to be and in many cases was incorrect (e.g.crds-cache-testor 'data/'.Note: ultimately we may want to move remaining tests away from using the 'crds_shared_group_cache' altogether - I elected not to do that for now because the majority of tests using it were fine and I'd rather not break something that didn't need fixing.
Decorated tests with observatory-based markers according to the test configuration and/or data being used in the test. For tests that don't use an observatory-based test configuration, the marker is "multimission". The primary intention here is to aid in troubleshooting setup/teardown problems. E.g. a test with an "hst" marker might be a mission-agnostic feature of CRDS, but it explicitly relies on the hst server, hst test data, etc.
added CRDS_PATH and CRDS_TESTING_CACHE to github actions ci.yml env
CCD-1434: Added metrics_logger decorator to Roman tests delivered with older builds (test_certify.py)