I've updated the IO_raw for tests with target_hdf5 & target_hsds backends.
Creates a test.conf.yaml to store configuration related to the actual test cases.
The test.conf.yaml can be used to turn on/off individual tests.
Here's an example run with the hs_username/hs_password set in the yaml:
Note that the hsds tests now show "n/a" for results.
I'd suggest updating the zarr benchmarks similarly. Put "GCS_Bucket" and such in a config, so that it can be easily disabled when running in environments without access to GCS.
I've updated the IO_raw for tests with target_hdf5 & target_hsds backends. Creates a test.conf.yaml to store configuration related to the actual test cases.
The test.conf.yaml can be used to turn on/off individual tests. Here's an example run with the hs_username/hs_password set in the yaml:
And a run with the default null for username and password:
Note that the hsds tests now show "n/a" for results.
I'd suggest updating the zarr benchmarks similarly. Put "GCS_Bucket" and such in a config, so that it can be easily disabled when running in environments without access to GCS.