Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-10692] Document how to define a test target #4861

Open
swift-ci opened this issue May 15, 2019 · 2 comments
Open

[SR-10692] Document how to define a test target #4861

swift-ci opened this issue May 15, 2019 · 2 comments
Labels

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-10692
Radar None
Original Reporter wimlewis (JIRA User)
Type Improvement
Status Reopened
Resolution
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Improvement, Documentation, Linux
Assignee None
Priority Medium

md5: faa32cc2e7a8b0a353d1015e5fd7077d

Issue Description:

Right now, there is almost no documentation of how to create and use a `.testTarget()`. Documentation consists of searching for peoples' blog posts on the subject, which are of course going to be obsolete and/or inaccurate most of the time.

Documentation should probably include things like:

  • Which files are required by `.testTarget()`? Where do they need to be, and relative to what directory?

  • What does the `path:` parameter affect?

  • What products, if any, need to be defined to go with a `.testTarget()`?

  • How this differs on Linux vs. Mac+Xcode

@ankitspd
Copy link
Member

SwiftPM's manifest API was recently revamped. Here is the target section: https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageDescription.md#target

@swift-ci
Copy link
Contributor Author

Comment by Wim Lewis (JIRA)

There is a small amount of documentation there (I did find it before filing this bug) but very little, just the parameter documentation for the function. I don't think it answers enough of the above questions (if any) to make it possible to use the `testTarget()` targets.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants