Andrew Bancroft • 4/15/2015

Testability Tip for Swift Developers – Public Over Private

Read Original

This article discusses a common challenge in Swift unit testing: how to test private functions. It reframes unit tests as clients of an API, arguing that only public code is easily testable. The author recommends using the 'public' access modifier over 'private' or 'internal' when possible to improve testability, while acknowledging the benefits of encapsulation and compiler optimizations for private code. The tip is aimed at Swift developers practicing Test-Driven Development.

0 comments
#unit testing #test-driven development #Swift
Testability Tip for Swift Developers – Public Over Private

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Limit token usage in Microsoft Agent Framework
Jesse Liberty • 1 votes
2
How to Roll Back AI Agents: Incident Response, Circuit Breakers, and Recovery Patterns
Paul Bryant • 1 votes
3
Avoiding Reasoning Model Failures with Microsoft Foundry
Luke Murray • 1 votes
4
When Your AI Agent Lies: Silent LLM Fallbacks
Luke Murray • 1 votes
5
Adding a custom MCP server to Claude and ChatGPT
Simon Willison • 1 votes
6
Testing AI prompts and comparing models with promptfoo
Tim Deschryver • 1 votes
7
Superlogical
Mitchell Hashimoto • 1 votes