Andrew Bancroft • 7/23/2014

Swift Access Control – Implications for Unit Testing

This article discusses the impact of Swift's access control (private, internal, public) on unit testing. It explains why unit tests break when classes are internal by default, as test targets are separate. The author presents two solutions: changing access to public or adding source files to the test target, recommending the former to avoid obscure issues. The piece emphasizes testing only public behavior, providing practical guidance for iOS developers.

0 comments

#unit testing #testing best practices #Access Control