#628 added 20 unit tests. Integration tests are really where we need further automation. Further action items:

Address the TODO items in Automate zppy tests #520. If we can get those steps automated, then we can effectively automate the entire process described at https://docs.e3sm.org/zppy/_build/html/main/dev_guide/release_testing.html
Once Automate zppy tests #520 is merged, we'll have a process we can run automatically every week. Ideally, we could set up some sort of cron process to run the Weekly tests weekly (rather than manually running them weekly).
Once the weekly tests are running automatically, it would further help to run some of the min-case cfg files automatically as well. Specifically, it would be great to have some sort of "if file was changed in this PR or recent commit history, then run min-case-X cfg" setup.
Look into mocking external dependencies rather than relying on real data paths, which can be finicky. Hackathon ideas for zppy #629 describes this further

Further automate tests #516

Description