Mac Disk Space for QA Testers: A Triage Order That Doesn’t Break Your Test Setup

Mac Disk Space for QA Testers: A Triage Order That Doesn’t Break Your Test Setup

Quick answer: QA Macs fill up because test tooling creates large, regenerable artifacts: simulator devices and runtimes, Xcode build data, Docker images, downloaded test browsers, and screen recordings. Delete in order of risk: build caches first, then stale simulators and containers, then recordings and old runtimes. Check what a folder holds before you remove it.

It’s 6:40 p.m. The regression build lands at 7:00. You tap “Run” on the suite and get “No space left on device,” or the simulator refuses to boot, or the screen recording you need for a bug report stops at 11 seconds.

Test machines rot differently from normal Macs. Nothing on yours is “junk” in the usual sense. Most of it is tooling that you will need again, and that is why people avoid cleaning it, or clean it too aggressively and lose an hour re-downloading a runtime.

This guide is the order I’d work through, from the least risky deletions to the most.

Step 0: Find out what is actually big (2 minutes)

Don’t guess. Open System Settings → General → Storage and note the total and the “Developer” category, if your macOS version shows one. Then look at the heavy folders directly:

 bash du -sh ~/Library/Developer/* 2>/dev/null | sort -h du -sh ~/Library/Caches/* 2>/dev/null | sort -h | tail -15

Two honest caveats:

“Purgeable” space is not guaranteed space. macOS reports caches and local snapshots as purgeable and reclaims them when it needs to, but that reclamation is not always instant. A test run that needs 20 GB at once can fail even when Storage says there is room. System Settings can lag behind reality after a big delete. Re-run df -h / to see the real number.

MacSnip sits in the menu bar and shows disk and Mac health at a glance, so you can see the number move while you clean instead of re-opening Settings.

Step 1: Build and tool caches (lowest risk)

These regenerate on the next build. The cost is time, not data.

Location What it is Safe to clear? ~/Library/Developer/Xcode/DerivedData Xcode build output and indexes Yes. The next build is slower. ~/Library/Caches/Homebrew (brew –cache) Downloaded bottles Yes. Run brew cleanup. ~/.npm npm download cache Yes. Use npm cache clean –force. ~/Library/Caches/Cypress, ~/Library/Caches/ms-playwright Downloaded Cypress and Playwright browser binaries Yes, but the next run re-downloads, and Playwright versions are pinned per project.

On macOS, the browser binaries that Playwright and Cypress download are often the surprise: a few hundred MB per browser version, multiplied by every version your projects pinned over a year. Old versions you no longer use can go. Keep the version your current project needs.

Do this one first: DerivedData. It is the largest regenerable folder on most iOS QA machines, and deleting it fixes a surprising number of weird build failures as a bonus.

Step 2: Simulators and emulators (medium risk, big payoff) iOS simulators

Every simulator device holds its own copy of apps, data and logs under ~/Library/Developer/CoreSimulator/Devices. Devices for runtimes you no longer have are dead weight:

 bash xcrun simctl list devices # see what exists xcrun simctl delete unavailable # remove devices whose runtime is gone

If a single device is bloated with test data, xcrun simctl erase

MacSnip app macsnip.app.