[SR-1135] swift test should always build
#5307
Assignees
Labels
Comments
|
CC @mxcl |
|
This leads to some very confusing behavior currently. For example, if you have no tests in Tests/, but you have built, then running `swift test` complains: $ swift test
error: no tests found to execute, create a test-module in `Tests` directoryEven though the tests actually are present. |
|
We can improve the error handling so it is clearer. The rationale for not building is that people want control, this way they have control. If they absolutely do not want to trigger a build, this allows it. Though we certainly can make it the default to build, and add a flag, and I tend to agree this should be the default, I'm just not 100% sure. |
|
PR: #494 |
|
Merged. |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Additional Detail from JIRA
md5: d7e2e4af49ddd7ba3c432daff4bae247
Issue Description:
Sometimes `swift test` doesn't build, e.g. if there is no .build directory it reports:
I think that we should try and have building be as much an "implementation detail" as possible, and try and always perform actions which are "consistent" in the sense that they match the state of the source. Of course, it is fine to support options to override this behavior, but I think it is the best default.
My goals are that we can work hard on the build system to try and ensure it is efficient enough that this is a good default for almost all situations.
The text was updated successfully, but these errors were encountered: