Which method better isolates Swift network tests from production credentials: a provider protocol or environment variables?

Answer

A credentials-provider protocol with initializer injection better isolates Swift network integration tests from production credentials than Xcode test environment variables guarded by #if DEBUG.

Production code stays free of test-only logic, no tokens are committed, and you can verify zero real requests by pairing the injected provider with a mock transport. Environment variables remain coupled to process environment and build configuration and can leak real secrets through misconfigured schemes or inherited CI env.

Confirmed facts

• Using a provider protocol requires a change to production initialization. The network client must accept a CredentialsProvider via its initializer instead of constructing or reading credentials itself. This is a confirmed design change that enables dependency injection without test-only code paths in production.
• Provider injection centralizes credential control in an explicit test double. Tests inject a test-only conformer returning static fake tokens. Production receives a real conformer built from secure storage.
• Environment variables with #if DEBUG keep literals out of source but still read ProcessInfo.processInfo.environment at runtime. #if DEBUG is a compile-time flag, not a runtime security boundary.

Likely risks and practical effects

• Environment variable approach is likely to expose real credentials if a DEBUG build runs in staging, a test scheme inherits CI secrets, or ProcessInfo state is not cleaned between tests. This is a likely risk, not a confirmed guarantee.
• Provider protocol alone does not prevent real network traffic. Tests must also inject a mock URLSession or URLProtocol to prove no production endpoints are hit.
• Test setup complexity differs. Protocol injection pairs naturally with a mock transport and requires no per-scheme env configuration. Environment variables require per-scheme env configuration, CI masking, and explicit cleanup of process environment between tests.

Steps needed for this case

1. Define a protocol and inject it.

protocol CredentialsProvider { func token() -> String }
final class NetworkClient {
  let provider: CredentialsProvider
  let session: URLSession
  init(provider: CredentialsProvider, session: URLSession) { self.provider = provider; self.session = session }
}

2. Production conformer reads from secure storage, not ProcessInfo. Tests use a test double returning a known fake token.
3. Inject a mock transport in tests and assert the client uses the fake token and records zero real requests.
4. Remove any ProcessInfo.environment reads from production client code and remove #if DEBUG credential branches.

Verification

• Review production network client initializers to confirm they accept a CredentialsProvider and do not call ProcessInfo.processInfo.environment directly.
• Run the test suite with an empty test environment and a test provider that returns a known fake token; assert the client uses the fake token and that a mock transport records zero real requests.
• Check Xcode test schemes to ensure no production secrets are set in environment variables and that DEBUG-only code paths are not present in release builds.

Assumption: you can modify production initializers to accept dependencies. If production objects cannot be changed, the recommendation changes. Confirm whether the current network client already accepts URLSession injection.