You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More than one comment on #894 felt that the OutputFileIdentifiers class not having enough information at its instantiation to know the ultimate file path of the on disk files should be addressed. It seems like this is related to the expectation in the tests that the expected results to check against are located at the same path but with an "expected" modifier in the file name.
Can we think of an elegant way to address both of these?
The text was updated successfully, but these errors were encountered:
yezr
changed the title
Find a more elegant way to ge the file path of results files and their expected counterparts during testing
Find a more elegant way to get the file path of results files and their expected counterparts during testing
Nov 11, 2024
More than one comment on #894 felt that the
OutputFileIdentifiers
class not having enough information at its instantiation to know the ultimate file path of the on disk files should be addressed. It seems like this is related to the expectation in the tests that the expected results to check against are located at the same path but with an "expected" modifier in the file name.Can we think of an elegant way to address both of these?
The text was updated successfully, but these errors were encountered: