Throw error if debug.yaml not found

[aciidgh]

Shows error this error if swift test is run before swift build

error: build the package using `swift build` before running tests

instead of

<unknown>:0: error: unable to attach DB: unable to open database
error: exit(1): swift-build-tool -f /Users/aciid/mycode/test/MyPackage/.build/debug.yaml test

[czechboy0]

Is there a reason to not automatically run swift build as the first step of swift test? To me running build, then test, then changing some test code and running test again - I'd assume that the changes would be applied. But since testing doesn't rebuild it doesn't, which initially confused me and I wonder whether it's not going to be confusing to newcomers as well.

I'd probably propose to automatically run build as the first step of test. Or is there a reason not to?

[aciidgh]

agreed, Utilities/bootstrap test also builds if not already built instead of exiting with error.
@mxcl suggestions?

[mxcl]

@czechboy0 we may change it. As it stands things are more flexible if you can control when the build happens entirely.

[mxcl]

guard seems more appropriate to me.

[aciidgh]

Fixed

[keith]

Looks like there's no newline at the end of this file.

[aciidgh]

fixed

[czechboy0]

@mxcl Makes sense. The way I think of it is in Xcode, the "easier" action is Run and Test, which actually mean Build+Run and Build+Test. Then you can trigger Run Without Building & Test Without Building manually, but that's more work.
In the same way I'd imagine we'd change the default here to build before testing, but we'd also add a flag to just test, something like swift build --test --no-rebuild or similar.