Facility to provide per-setup atom data as well as save report locally. #653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR focuses on adding flexibility to current integration testing infrastructure.
Facility for Atom Data files;
kurucz_cd23_chianti_H_He.h5
) could be provided using the--atomic-dataset
flag. Instead of this, the integration tests can now use the atom data file specified in the YAML config of a particular setup used for integration tests (in the sub directories oftardis/tests/integration_tests
).fetch
is set to local, then files will be taken fromdirpath
andurl
field will be ignored. Even writing it in isn't necessary in those cases. It will be the opposite case iffetch: "remote"
.Local saving of report:
save_mode
is set to local, then files will be taken fromdirpath
anddokuwiki
section will be ignored. Even writing it in isn't necessary in those cases. It will be the opposite case ifsave_mode: "remote"
.NOTE:
--remote-data
flag as argument.