This PR is set up to let you see the unique commits on top of the 464 branch. It can be retargetted at dev if we want to merge both 464 & 467 in a snigle PR.
Here you can see the text file expectation maker, which is just a list of strings, which pytest already knows how to compare. Also make the test environment's directory-under-observation be configurable, so some tests can look at an export dir while others look at the data repo. Also run filesystem observation such that the user has a chance to do setup activity that won't be counted as part of the test.
And make t_project and t_stats pass in the new regime (for modis & merra).
This PR is set up to let you see the unique commits on top of the 464 branch. It can be retargetted at dev if we want to merge both 464 & 467 in a snigle PR.
Here you can see the text file expectation maker, which is just a list of strings, which pytest already knows how to compare. Also make the test environment's directory-under-observation be configurable, so some tests can look at an export dir while others look at the data repo. Also run filesystem observation such that the user has a chance to do setup activity that won't be counted as part of the test.
And make t_project and t_stats pass in the new regime (for modis & merra).