[swift-evolution] [Review] SE-0019 Swift Testing (Package Manager)
cantrell at pobox.com
Tue Jan 5 13:40:07 CST 2016
A few requests for clarification from the proposal authors:
1. The proposal talks in several places about “test modules” (for example, “test-module is created per subdirectory of Tests”). How do these test modules interact with Package.swift? Does each of them have a separate target? If so, how is the test module name specified in the Target(…) entry?
2. Perhaps answered by #1, how does Package.swift specify test-only dependencies (e.g. Quick) that are necessary to build tests, but should not be exported to downstream projects?
3. You propose that “building a module also builds that module's corresponding tests.” Does this apply only to the top-level package, or to all of its dependencies? For example, if my FooApp depends on BarLib, and BarLib’s tests depend on HugeFancyTestFramework, do I have to download and compile HugeFancyTestFramework in order to build FooApp? (Hopefully not!)
I apologize if these questions are already answered in the proposal. I’m not sure I caught every subtlety of the writeup.
> On Jan 5, 2016, at 1:06 PM, Rick Ballard via swift-evolution <swift-evolution at swift.org> wrote:
> Hello Swift community,
> The review of “Swift Testing” for the Package Manager begins now and runs through Thursday, January 7th. The proposal is available here:
> For this particular review, please note that a significant amount of discussion history is available in the original pull request for the proposal:
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> or, if you would like to keep your feedback private, directly to the review manager.
> What goes into a review?
> The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
> * What is your evaluation of the proposal?
> * Is the problem being addressed significant enough to warrant a change to Swift?
> * Does this proposal fit well with the feel and direction of Swift?
> * If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> More information about the Swift evolution process is available at
> Thank you,
> - Rick
> Review Manager
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution