My team is running into issues with the Github Actions checks when making/merging pull requests. Specifically, IO Redirection is causing us issues - this is due to our error handling printing out filepaths. Since Paths.toString() uses the system-dependent name separator, the EXPECTED.txt is bound to not match with the ACTUAL.txt on either Mac/Linux or Windows. (See https://github.com/AY2223S1-CS2113-T17-4/tp/pull/47/checks - the Windows gradle test fail is unrelated and has been fixed)
While we can remove the printing of filepaths, we feel this is a feature that improves user experience and helps users troubleshoot errors, and removing it for the sake of passing a test is counterintuitive to the project as a whole. Are there any ways we can make this test pass (or suppress the test for those lines) without removing functionality?
My team is running into issues with the Github Actions checks when making/merging pull requests. Specifically, IO Redirection is causing us issues - this is due to our error handling printing out filepaths. Since Paths.toString() uses the system-dependent name separator, the EXPECTED.txt is bound to not match with the ACTUAL.txt on either Mac/Linux or Windows. (See https://github.com/AY2223S1-CS2113-T17-4/tp/pull/47/checks - the Windows gradle test fail is unrelated and has been fixed)
While we can remove the printing of filepaths, we feel this is a feature that improves user experience and helps users troubleshoot errors, and removing it for the sake of passing a test is counterintuitive to the project as a whole. Are there any ways we can make this test pass (or suppress the test for those lines) without removing functionality?