It took me two months to figure out what Swift could do as a function of programming language, and now it has shifted to using Swift to develop library files.
It took me a day to finally find out that the swift features I had done before were quite enjoyable, and I found that I still needed to learn how to do some of the most basic chores, and here are some of the problems I encountered in the default framework test settings.
I have some problems with the project of creating a new cocoa framework in swift language.
However, by default, these problems will be followed by the test, and you will mistakenly assume that the "cmd+u" test will run after you complete an app, then you are wrong. Most of the options in the "Product" menu are not available, and when you try to use the shortcut, you will suddenly hear "you can't do this" as if the heart is sinking in a general tone.
Because, by default, the test package is not added to the test configuration of the framework build scenario. The workaround is to name your frame "test" (which is how I named it), then select it and then click on "Edit Scheme" (edit Scheme ...). :
Then go to the "test" option and click on the "+" button in the lower left corner of the detailed interface on the right:
Check your test package (see why I named Test):
Now that all the test shortcut keys are available, you can start working (if the shortcut keys aren't working then just because your frame itself doesn't work).
Good test!
My Test experience sharing on the SWIFT framework on Xcode 6