Skip to content

armgit / peel

Public Imported from GitHub
0

Uninstall Mac apps with every file they leave behind, and see why each belongs. Free up space, fine-tune macOS, and set up Terminal.

CONTRIBUTING.md says why a test scans a made-up app

Țugui Dragoș6cff8b8897fe
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4412cc37..fcf526c4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -51,10 +51,12 @@ swift build --package-path Packages/PeelCore -Xswiftc -warnings-as-errors
Tests run through the code Peel runs, on the Mac running them: a scan asks this Mac's Launch Services and reads its
system apps and a real disk, since an answer about Homebrew, launchd, Launch Services, or the disk is worth little
against a mock. A stand-in is only for what a Mac can't do on demand, such as a folder that never answers, and the
-files a test scans sit in a temporary home, never in yours. Some tests read this Mac on purpose, so they are slower
-and depend on what you have installed. The slowest scans every app installed here, in full, to check that nothing
-Peel would select is refused or shared. It takes minutes, so it runs only when asked for, and it is worth running
-before a release:
+files a test scans sit in a temporary home, never in yours. When a test expects Peel to select an app's files, the
+app it scans is a made-up one, under a domain kept for examples (such as `net.example`): a real app may be installed
+anywhere on the Mac running the test, and another copy of it keeps those files. Some tests read this Mac on purpose,
+so they are slower and depend on what you have installed. The slowest scans every app installed here, in full, to
+check that nothing Peel would select is refused or shared. It takes minutes, so it runs only when asked for, and it
+is worth running before a release:
```bash
PEEL_TEST_THIS_MAC=1 swift test --package-path Packages/PeelCore --filter SuggestedSelectionOnThisMacTests