This removes a flaky test that wasn't doing much for us: in the case that there's a valid ~/.sauced.yaml in the user's home directory, this test would blow up.
We could in theory build some tooling to completely isolate the tests in a separate in memory file system, but that would be alot of effort for standard lib functionality that would probably be better served by e2e tests.
Description
This removes a flaky test that wasn't doing much for us: in the case that there's a valid
~/.sauced.yamlin the user's home directory, this test would blow up.We could in theory build some tooling to completely isolate the tests in a separate in memory file system, but that would be alot of effort for standard lib functionality that would probably be better served by e2e tests.
Related Tickets & Documents
Closes: https://github.com/open-sauced/pizza-cli/issues/132
Steps to QA
just test- tests pass with a valid~/.sauced.yamlin the user's home directory:Tier (staff will fill in)