Swift 2 introduced the
@testable keyword so that unit test targets could access internal APIs of frameworks like so:
@testable import MyFramework
Without this keyword the only alternative was to make APIs public, defeating the purpose of access controls.
So check this out:
@testable also works in Playgrounds!
Paired with elegant use of the inline documentation renderer, it's now possible to write Playgrounds that function as interactive internal documentation. This sets the stage for great new forms of technical documentation.