Closed jonmaddock closed 2 months ago
I have looked to see if the scripts in the process/io
subpackage have tests or not. Here is a summary:
configuration.py
no need to testin_dat.py
no need to add a test for this as the IN.DAT file format will be removed in the futuremfile2dict.py
this already has a testmfile_comparison.py
no need to add a test for this as the MFILE.DAT file format will be removed in the futuremfile.py
no need to add a test for this as the MFILE.DAT file format will be removed in the futuremfile_to_csv.py
this is already testedobsolete_vars.py
no need to test as this just contains a dictionary of obsolete variables and their replacements/helpful messagesplot_proc.py
this already has a testplot_radial_build.py
this already has a testplot_sankey.py
this already has a testplot_scans.py
this already has a testplot_solutions.py
this already has a testprocess_config.py
no need to testprocess_funcs.py
no need to testpython_fortran_dicts.py
no need to testsankey_funcs.py
this is indirectly tested through test_plot_sankey.py
variable_metadata.py
no need to test This means that the process/io
subpackage is currently adequately tested and so no more tests need to be added, so will close this issue.
Some modules within the
process.io
subpackage are not yet tested: these are the modules that deal with manipulating, processing or visualising Process's input/output files. Before the Python data structure work commences, it would be advantageous to write tests for any of these modules that will still be required in some form after the Python conversion work. Which modules to test should be decided, and then the integration tests implemented.