blocks|key|321343|text|当单元测试工具运行您的代码时，您的单元测试包是而不是主包。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|321344|即使您正在运行测试，而不是您的应用程序，您的应用程序包仍然是主包。(这可能会防止您正在测试的代码搜索错误的包。)因此，如果您将资源文件添加到单元测试包中，则在搜索主包时将找不到它。如果将上一行替换为：|321345|NSBundle+*bundle+=+[NSBundle+bundleForClass:[self+class]];
NSString+*path+=+[bundle+pathForResource:@"foo"+ofType:@"txt"];|code-block|syntax|javascript|321346|然后，您的代码将搜索您的单元测试类所在的包，一切都会好起来的。|321347|entityMap^0|N|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

When the unit test harness runs your code, your unit test bundle is NOT the main bundle.

Even though you are running tests, not your application, your application bundle is still the main bundle. (Presumably, this prevents the code you are testing from searching the wrong bundle.) Thus, if you add a resource file to the unit test bundle, you won't find it if search the main bundle. If you replace the above line with:

<pre><code>NSBundle *bundle = [NSBundle bundleForClass:[self class]];
NSString *path = [bundle pathForResource:@"foo" ofType:@"txt"];
</code></pre>

Then your code will search the bundle that your unit test class is in, and everything will be fine.

blocks|key|325919|text|一个Swift实现：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|325920|Swift+2|offset|length|style|BOLD|325921|let+testBundle+=+NSBundle(forClass:+self.dynamicType)
let+fileURL+=+testBundle.URLForResource("imageName",+withExtension:+"png")
XCTAssertNotNil(fileURL)|code-block|syntax|javascript|325922|Swift+3、Swift+4|325923|let+testBundle+=+Bundle(for:+type(of:+self))
let+filePath+=+testBundle.path(forResource:+"imageName",+ofType:+"png")
XCTAssertNotNil(filePath)|325924|捆绑包提供了发现配置的主路径和测试路径的方法：|325925|@testable+import+Example

class+ExampleTests:+XCTestCase+{
++++++++
++++func+testExample()+{
++++++++let+bundleMain+=+Bundle.main
++++++++let+bundleDoingTest+=+Bundle(for:+type(of:+self+))
++++++++let+bundleBeingTested+=+Bundle(identifier:+"com.example.Example")!
++++++++++++++++
++++++++print("bundleMain.bundlePath+:+\(bundleMain.bundlePath)")
++++++++//+…/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Xcode/Agents
++++++++print("bundleDoingTest.bundlePath+:+\(bundleDoingTest.bundlePath)")
++++++++//+…/PATH/TO/Debug/ExampleTests.xctest
++++++++print("bundleBeingTested.bundlePath+:+\(bundleBeingTested.bundlePath)")
++++++++//+…/PATH/TO/Debug/Example.app
++++++++
++++++++print("bundleMain+=+"+%2B+bundleMain.description)+//+Xcode+Test+Agent
++++++++print("bundleDoingTest+=+"+%2B+bundleDoingTest.description)+//+Test+Case+Bundle
++++++++print("bundleUnderTest+=+"+%2B+bundleBeingTested.description)+//+App+Bundle|325926|在Xcode6%7C7%7C8%7C9中，单元测试包路径将在Developer/Xcode/DerivedData中，类似于...|CODE|325927|/Users/
++UserName/
++++Library/
++++++Developer/
++++++++Xcode/
++++++++++DerivedData/
++++++++++++App-qwertyuiop.../
++++++++++++++Build/
++++++++++++++++Products/
++++++++++++++++++Debug-iphonesimulator/
++++++++++++++++++++AppTests.xctest/
++++++++++++++++++++++foo.txt|325928|..。它与Developer/CoreSimulator/Devices+常规(非单元测试)包路径是分开的|325929|/Users/
++UserName/
++++Library/
++++Developer/
++++++CoreSimulator/
++++++++Devices/
++++++++++_UUID_/
++++++++++++data/
++++++++++++++Containers/
++++++++++++++++Bundle/
++++++++++++++++++Application/
++++++++++++++++++++_UUID_/
++++++++++++++++++++++App.app/|325930|另请注意，默认情况下，单元测试可执行文件与应用程序代码链接。但是，单元测试代码应该只在测试包中具有Target成员资格。应用程序代码在应用程序捆绑包中应该只有Target成员资格。在运行时，单元测试目标包是。|325931|Swift包管理器(SPM)+4:|325932|let+testBundle+=+Bundle(for:+type(of:+self))+
print("testBundle.bundlePath+=+\(testBundle.bundlePath)+")|325933|注意:默认情况下，命令行swift+test将创建一个MyProjectPackageTests.xctest测试包。并且，swift+package+generate-xcodeproj将创建一个MyProjectTests.xctest测试包。这些不同的测试包有不同的路径。此外，不同的测试包可能具有一些内部目录结构和__的内容差异。|325934|在任何一种情况下，.bundlePath和.bundleURL都将返回当前在macOS上运行的测试包的路径。然而，Bundle目前还没有在Ubuntu+Linux上实现。|325935|此外，命令行swift+build和swift+test目前不提供复制资源的机制。|325936|但是，通过一些努力，可以设置在Ubuntu、macOS命令行和macOS命令行环境中使用Swift+Package+Manger的进程。在这里可以找到一个例子：004.4'2+SW+Dev+Swift+Package+Manager+(SPM)+With+Resources+Qref|325937|另请参阅：Use+resources+in+unit+tests+with+Swift+Package+Manager|325938|Swift包管理器(SwiftPM)+5.3|325939|Swift+5.3包含带有"Status：Implemented+(Swift+5.3)__“的演进提案。:-)|325940|325941|资源并不总是供包的客户端使用；资源的一次使用可能包括仅由单元测试所需的测试装置。这样的资源不会与库代码一起并入包的客户端，而是仅在运行包的测试时使用。|blockquote|325942|325943|325944|325945|在target和testTarget+API中添加新的resources参数，以允许显式声明资源文件。|unordered-list-item|325946|325947|SwiftPM使用文件系统约定来确定属于包中每个目标的源文件集:具体地说，目标的源文件是位于目标的指定“目标目录”下的源文件。默认情况下，这是一个与目标同名的目录，位于"Sources“(对于常规目标)或"Tests”(对于测试目标)中，但可以在包清单中自定义此位置。|325948|325949|+//获取DefaultSettings.plist文件的路径。let+path+=+Bundle.module.path(forResource："DefaultSettings"，ofType："plist")+//加载可以捆绑在资产归档中的镜像。let+image+=UIImage(名称："MyIcon"，in:+Bundle.module，compatibleWith:+UITraitCollection(userInterfaceStyle：.dark))+//在编译的金属着色器库中查找顶点函数。让着色器=尝试着色器(mtlDevice.makeDefaultLibrary:Bundle.module).makeFunction(名称："vertexShader")+//加载纹理。让texture+=+MTKTextureLoader(device:+mtlDevice).newTexture(名称：“草”，scaleFactor:+1.0，捆绑:+Bundle.module，选项:选项)|325950|325951|325952|示例|325953|//+swift-tools-version:5.3
import+PackageDescription

++targets:+[
++++.target(
++++++name:+"CLIQuickstartLib",
++++++dependencies:+[],
++++++resources:+[
++++++++//+Apply+platform-specific+rules.
++++++++//+For+example,+images+might+be+optimized+per+specific+platform+rule.
++++++++//+If+path+is+a+directory,+the+rule+is+applied+recursively.
++++++++//+By+default,+a+file+will+be+copied+if+no+rule+applies.
++++++++.process("Resources"),
++++++]),
++++.testTarget(
++++++name:+"CLIQuickstartLibTests",
++++++dependencies:+[],
++++++resources:+[
++++++++//+Copy+directories+as-is.+
++++++++//+Use+to+retain+directory+structure.
++++++++//+Will+be+at+top+level+in+bundle.
++++++++.copy("Resources"),
++++++]),|325954|最新一期|325955|325956|Swift+5.3+SPM+Resources+in+tests+uses+wrong+bundle+path?|325957|Swift+Package+Manager+-+Resources+in+test+targets|325958|325959|Xcode|325960|Bundle.module是由SwiftPM生成的(请参阅)，因此在由Xcode构建时不会出现在中。|325961|在Xcode中，一种类似的方法是手动将Resources引用文件夹添加到模块中，添加Xcode构建阶段copy以将Resource放入某个*.bundle目录中，并为Xcode构建添加#ifdef+Xcode编译器指令以使用资源。|325962|#if+Xcode+
extension+Foundation.Bundle+{
++
++///+Returns+resource+bundle+as+a+`Bundle`.
++///+Requires+Xcode+copy+phase+to+locate+files+into+`*.bundle`
++///+or+`ExecutableNameTests.bundle`+for+test+resources
++static+var+module:+Bundle+=+{
++++var+thisModuleName+=+"CLIQuickstartLib"
++++var+url+=+Bundle.main.bundleURL
++++
++++for+bundle+in+Bundle.allBundles+
++++++where+bundle.bundlePath.hasSuffix(".xctest")+{
++++++url+=+bundle.bundleURL.deletingLastPathComponent()
++++++thisModuleName+=+thisModuleName.appending("Tests")
++++}
++++
++++url+=+url.appendingPathComponent("\(thisModuleName).bundle")
++++
++++guard+let+bundle+=+Bundle(url:+url)+else+{
++++++fatalError("Bundle.module+could+not+load:+\(url.path)")
++++}
++++
++++return+bundle
++}()
++
++///+Directory+containing+resource+bundle
++static+var+moduleDir:+URL+=+{
++++var+url+=+Bundle.main.bundleURL
++++for+bundle+in+Bundle.allBundles+
++++++where+bundle.bundlePath.hasSuffix(".xctest")+{
++++++//+remove+'ExecutableNameTests.xctest'+path+component
++++++url+=+bundle.bundleURL.deletingLastPathComponent()
++++}
++++return+url
++}()
++
}
#endif|325963|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/marc-medley/599d387337e29c74624816a57f2e4c12|1|https://stackoverflow.com/questions/47177036/use-resources-in-unit-tests-with-swift-package-manager/49090702#49090702|2|https://forums.swift.org/t/swift-5-3-spm-resources-in-tests-uses-wrong-bundle-path/37051|3|https://github.com/Nef10/SPMResourcesInTest^0|0|0|7|0|0|0|F|0|0|0|0|F|7|O|R|0|0|5|V|11|C|0|0|0|0|H|0|0|C|A|R|S|1Q|W|2R|L|4A|7|0|9|B|L|A|1L|6|0|6|B|I|A|0|28|1Q|0|0|5|1I|1|0|0|M|0|L|N|0|0|0|0|0|0|1|6|8|A|R|9|0|0|0|0|0|0|0|0|2|0|0|0|4|0|0|0|1K|2|0|0|1D|3|0|0|0|5|0|0|D|0|J|9|1F|4|1L|8|1X|8|2K|C|0|0^^$0|@$1|2|3|4|5|6|7|33|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|34|8|@$D|35|E|36|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|37|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|38|8|@$D|39|E|3A|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|3B|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|3C|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|3D|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|3E|8|@$D|3F|E|3G|F|G]|$D|3H|E|3I|F|W]]|9|@]|A|$]]|$1|X|3|Y|5|J|7|3J|8|@]|9|@]|A|$K|L]]|$1|Z|3|10|5|6|7|3K|8|@$D|3L|E|3M|F|W]|$D|3N|E|3O|F|G]]|9|@]|A|$]]|$1|11|3|12|5|J|7|3P|8|@]|9|@]|A|$K|L]]|$1|13|3|14|5|6|7|3Q|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|3R|8|@$D|3S|E|3T|F|G]]|9|@]|A|$]]|$1|17|3|18|5|J|7|3U|8|@]|9|@]|A|$K|L]]|$1|19|3|1A|5|6|7|3V|8|@$D|3W|E|3X|F|W]|$D|3Y|E|3Z|F|W]|$D|40|E|41|F|W]|$D|42|E|43|F|W]|$D|44|E|45|F|G]]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|46|8|@$D|47|E|48|F|W]|$D|49|E|4A|F|W]|$D|4B|E|4C|F|W]]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|4D|8|@$D|4E|E|4F|F|W]|$D|4G|E|4H|F|W]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|4I|8|@]|9|@$D|4J|E|4K|1|4L]]|A|$]]|$1|1H|3|1I|5|6|7|4M|8|@]|9|@$D|4N|E|4O|1|4P]]|A|$]]|$1|1J|3|1K|5|6|7|4Q|8|@$D|4R|E|4S|F|G]]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|4T|8|@$D|4U|E|4V|F|G]]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|4W|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|1Q|7|4X|8|@]|9|@]|A|$]]|$1|1R|3|-4|5|6|7|4Y|8|@]|9|@]|A|$]]|$1|1S|3|-4|5|6|7|4Z|8|@]|9|@]|A|$]]|$1|1T|3|-4|5|6|7|50|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|1W|7|51|8|@$D|52|E|53|F|W]|$D|54|E|55|F|W]|$D|56|E|57|F|W]]|9|@]|A|$]]|$1|1X|3|-4|5|6|7|58|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|6|7|59|8|@]|9|@]|A|$]]|$1|20|3|-4|5|6|7|5A|8|@]|9|@]|A|$]]|$1|21|3|22|5|1Q|7|5B|8|@]|9|@]|A|$]]|$1|23|3|-4|5|6|7|5C|8|@]|9|@]|A|$]]|$1|24|3|-4|5|6|7|5D|8|@]|9|@]|A|$]]|$1|25|3|26|5|6|7|5E|8|@$D|5F|E|5G|F|G]]|9|@]|A|$]]|$1|27|3|28|5|J|7|5H|8|@]|9|@]|A|$K|L]]|$1|29|3|2A|5|6|7|5I|8|@$D|5J|E|5K|F|G]]|9|@]|A|$]]|$1|2B|3|-4|5|6|7|5L|8|@]|9|@]|A|$]]|$1|2C|3|2D|5|1W|7|5M|8|@]|9|@$D|5N|E|5O|1|5P]]|A|$]]|$1|2E|3|2F|5|1W|7|5Q|8|@]|9|@$D|5R|E|5S|1|5T]]|A|$]]|$1|2G|3|-4|5|6|7|5U|8|@]|9|@]|A|$]]|$1|2H|3|2I|5|6|7|5V|8|@$D|5W|E|5X|F|G]]|9|@]|A|$]]|$1|2J|3|2K|5|6|7|5Y|8|@$D|5Z|E|60|F|W]]|9|@]|A|$]]|$1|2L|3|2M|5|6|7|61|8|@$D|62|E|63|F|W]|$D|64|E|65|F|W]|$D|66|E|67|F|W]|$D|68|E|69|F|W]|$D|6A|E|6B|F|W]]|9|@]|A|$]]|$1|2N|3|2O|5|J|7|6C|8|@]|9|@]|A|$K|L]]|$1|2P|3|-4|5|6|7|6D|8|@]|9|@]|A|$]]]|2Q|$2R|$5|2S|2T|2U|A|$2V|2W]]|2X|$5|2S|2T|2U|A|$2V|2Y]]|2Z|$5|2S|2T|2U|A|$2V|30]]|31|$5|2S|2T|2U|A|$2V|32]]]]

A Swift implementation:
Swift 2
<pre class="lang-swift prettyprint-override"><code>let testBundle = NSBundle(forClass: self.dynamicType)
let fileURL = testBundle.URLForResource(&quot;imageName&quot;, withExtension: &quot;png&quot;)
XCTAssertNotNil(fileURL)
</code></pre>
Swift 3, Swift 4
<pre class="lang-swift prettyprint-override"><code>let testBundle = Bundle(for: type(of: self))
let filePath = testBundle.path(forResource: &quot;imageName&quot;, ofType: &quot;png&quot;)
XCTAssertNotNil(filePath)
</code></pre>
Bundle provides ways to discover the main and test paths for your configuration:
<pre class="lang-swift prettyprint-override"><code>@testable import Example

class ExampleTests: XCTestCase {
 
 func testExample() {
 let bundleMain = Bundle.main
 let bundleDoingTest = Bundle(for: type(of: self ))
 let bundleBeingTested = Bundle(identifier: &quot;com.example.Example&quot;)!
 
 print(&quot;bundleMain.bundlePath : \(bundleMain.bundlePath)&quot;)
 // …/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Xcode/Agents
 print(&quot;bundleDoingTest.bundlePath : \(bundleDoingTest.bundlePath)&quot;)
 // …/PATH/TO/Debug/ExampleTests.xctest
 print(&quot;bundleBeingTested.bundlePath : \(bundleBeingTested.bundlePath)&quot;)
 // …/PATH/TO/Debug/Example.app
 
 print(&quot;bundleMain = &quot; + bundleMain.description) // Xcode Test Agent
 print(&quot;bundleDoingTest = &quot; + bundleDoingTest.description) // Test Case Bundle
 print(&quot;bundleUnderTest = &quot; + bundleBeingTested.description) // App Bundle
</code></pre>
In Xcode 6|7|8|9, a unit-test bundle path will be in <code>Developer/Xcode/DerivedData</code> something like ...
<pre><code>/Users/
 UserName/
 Library/
 Developer/
 Xcode/
 DerivedData/
 App-qwertyuiop.../
 Build/
 Products/
 Debug-iphonesimulator/
 AppTests.xctest/
 foo.txt
</code></pre>
... which is separate from the <code>Developer/CoreSimulator/Devices</code> regular (non-unit-test) bundle path:
<pre><code>/Users/
 UserName/
 Library/
 Developer/
 CoreSimulator/
 Devices/
 _UUID_/
 data/
 Containers/
 Bundle/
 Application/
 _UUID_/
 App.app/
</code></pre>
Also note the unit test executable is, by default, linked with the application code. However, the unit test code should only have Target Membership in just the test bundle. The application code should only have Target Membership in the application bundle. At runtime, the unit test target bundle is <a href="https://stackoverflow.com/questions/32639263/changed-load-method-order-in-xcode-7/33851001#33851001">injected into the application bundle for execution</a>.
Swift Package Manager (SPM) 4:
<pre class="lang-swift prettyprint-override"><code>let testBundle = Bundle(for: type(of: self)) 
print(&quot;testBundle.bundlePath = \(testBundle.bundlePath) &quot;)
</code></pre>
Note: By default, the command line <code>swift test</code> will create a <code>MyProjectPackageTests.xctest</code> test bundle. And, the <code>swift package generate-xcodeproj</code> will create a <code>MyProjectTests.xctest</code> test bundle. These different test bundles have different paths. Also, the different test bundles may have some internal directory structure and content differences.
In either case, the <code>.bundlePath</code> and <code>.bundleURL</code> will return the path of test bundle currently being run on macOS. However, <code>Bundle</code> is not currently implemented for Ubuntu Linux.
Also, command line <code>swift build</code> and <code>swift test</code> do not currently provide a mechanism for copying resources.
However, with some effort, it is possible to set up processes for using the Swift Package Manger with resources in the macOS Xcode, macOS command line, and Ubuntu command line environments. One example can be found here: <a href="https://gist.github.com/marc-medley/599d387337e29c74624816a57f2e4c12" rel="noreferrer">004.4'2 SW Dev Swift Package Manager (SPM) With Resources Qref</a>
See also: <a href="https://stackoverflow.com/questions/47177036/use-resources-in-unit-tests-with-swift-package-manager/49090702#49090702">Use resources in unit tests with Swift Package Manager</a>
Swift Package Manager (SwiftPM) 5.3
Swift 5.3 includes <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0271-package-manager-resources.md" rel="noreferrer">Package Manager Resources SE-0271</a> evolution proposal with &quot;Status: Implemented (Swift 5.3)&quot;. :-)
<blockquote>
Resources aren't always intended for use by clients of the package; one use of resources might include test fixtures that are only needed by unit tests. Such resources would not be incorporated into clients of the package along with the library code, but would only be used while running the package's tests.
<ul>
<li>Add a new <code>resources</code> parameter in <code>target</code> and <code>testTarget</code> APIs to allow declaring resource files explicitly.</li>
</ul>
SwiftPM uses file system conventions for determining the set of source files that belongs to each target in a package: specifically, a target's source files are those that are located underneath the designated &quot;target directory&quot; for the target. By default this is a directory that has the same name as the target and is located in &quot;Sources&quot; (for a regular target) or &quot;Tests&quot; (for a test target), but this location can be customized in the package manifest.
</blockquote>
<blockquote>
<pre class="lang-swift prettyprint-override"><code>// Get path to DefaultSettings.plist file.
let path = Bundle.module.path(forResource: &quot;DefaultSettings&quot;, ofType: &quot;plist&quot;)

// Load an image that can be in an asset archive in a bundle.
let image = UIImage(named: &quot;MyIcon&quot;, in: Bundle.module, compatibleWith: UITraitCollection(userInterfaceStyle: .dark))

// Find a vertex function in a compiled Metal shader library.
let shader = try mtlDevice.makeDefaultLibrary(bundle: Bundle.module).makeFunction(name: &quot;vertexShader&quot;)

// Load a texture.
let texture = MTKTextureLoader(device: mtlDevice).newTexture(name: &quot;Grass&quot;, scaleFactor: 1.0, bundle: Bundle.module, options: options)
</code></pre>
</blockquote>
Example
<pre class="lang-swift prettyprint-override"><code>// swift-tools-version:5.3
import PackageDescription

 targets: [
 .target(
 name: &quot;CLIQuickstartLib&quot;,
 dependencies: [],
 resources: [
 // Apply platform-specific rules.
 // For example, images might be optimized per specific platform rule.
 // If path is a directory, the rule is applied recursively.
 // By default, a file will be copied if no rule applies.
 .process(&quot;Resources&quot;),
 ]),
 .testTarget(
 name: &quot;CLIQuickstartLibTests&quot;,
 dependencies: [],
 resources: [
 // Copy directories as-is. 
 // Use to retain directory structure.
 // Will be at top level in bundle.
 .copy(&quot;Resources&quot;),
 ]),
</code></pre>
Current Issue
<ul>
<li><a href="https://forums.swift.org/t/swift-5-3-spm-resources-in-tests-uses-wrong-bundle-path/37051" rel="noreferrer">Swift 5.3 SPM Resources in tests uses wrong bundle path?</a></li>
<li><a href="https://github.com/Nef10/SPMResourcesInTest" rel="noreferrer">Swift Package Manager - Resources in test targets</a></li>
</ul>
Xcode
<code>Bundle.module</code> is generated by SwiftPM (see <a href="https://github.com/apple/swift-package-manager/blob/master/Sources/Build/BuildPlan.swift" rel="noreferrer">Build/BuildPlan.swift SwiftTargetBuildDescription generateResourceAccessor()</a>) and thus not present in <a href="https://developer.apple.com/documentation/foundation/bundle" rel="noreferrer">Foundation.Bundle</a> when built by Xcode.
A comparable approach in Xcode would be to manually add a <code>Resources</code> reference folder to the module, add an Xcode build phase <code>copy</code> to put the <code>Resource</code> into some <code>*.bundle</code> directory, and add a <code>#ifdef Xcode</code> compiler directive for the Xcode build to work with the resources.
<pre class="lang-swift prettyprint-override"><code>#if Xcode 
extension Foundation.Bundle {
 
 /// Returns resource bundle as a `Bundle`.
 /// Requires Xcode copy phase to locate files into `*.bundle`
 /// or `ExecutableNameTests.bundle` for test resources
 static var module: Bundle = {
 var thisModuleName = &quot;CLIQuickstartLib&quot;
 var url = Bundle.main.bundleURL
 
 for bundle in Bundle.allBundles 
 where bundle.bundlePath.hasSuffix(&quot;.xctest&quot;) {
 url = bundle.bundleURL.deletingLastPathComponent()
 thisModuleName = thisModuleName.appending(&quot;Tests&quot;)
 }
 
 url = url.appendingPathComponent(&quot;\(thisModuleName).bundle&quot;)
 
 guard let bundle = Bundle(url: url) else {
 fatalError(&quot;Bundle.module could not load: \(url.path)&quot;)
 }
 
 return bundle
 }()
 
 /// Directory containing resource bundle
 static var moduleDir: URL = {
 var url = Bundle.main.bundleURL
 for bundle in Bundle.allBundles 
 where bundle.bundlePath.hasSuffix(&quot;.xctest&quot;) {
 // remove 'ExecutableNameTests.xctest' path component
 url = bundle.bundleURL.deletingLastPathComponent()
 }
 return url
 }()
 
}
#endif
</code></pre>

blocks|key|321376|text|确认资源已添加到测试目标。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|321377|​|321378|📷|atomic|offset|length|321379|321380|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/9c9f8e257bd3f06cf94ebe3ce6d8f000.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Confirm that the resource is added to the test target.

<a href="https://i.stack.imgur.com/JkfQN.png" rel="noreferrer"><img src="https://i.stack.imgur.com/JkfQN.png" alt="enter image description here"></a>

blocks|key|323836|text|在swift+3中，语法self.dynamicType已被弃用，请使用以下语法|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|323837|let+testBundle+=+Bundle(for:+type(of:+self))
let+fooTxtPath+=+testBundle.path(forResource:+"foo",+ofType:+"txt")|code-block|syntax|javascript|323838|或|323839|let+fooTxtURL+=+testBundle.url(forResource:+"foo",+withExtension:+"txt")|323840|entityMap^0|C|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

With swift Swift 3 the syntax <code>self.dynamicType</code> has been deprecated, use this instead

<pre><code>let testBundle = Bundle(for: type(of: self))
let fooTxtPath = testBundle.path(forResource: "foo", ofType: "txt")
</code></pre>

or 

<pre><code>let fooTxtURL = testBundle.url(forResource: "foo", withExtension: "txt")
</code></pre>

blocks|key|321482|text|如果您的项目中有多个目标，则需要在目标成员资格中提供的不同目标之间添加资源，并且可能需要在不同的目标之间切换，如下图所示|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|321483|​|321484|📷|atomic|321485|321486|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/24ce5ba5fd121fa53999f72c7f1ef0ec.png|imageAlt^0|H|6|1C|2|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|K|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

if you have multiple target in your project then you need to add resources between different target available in the Target Membership and you may need to switch between different Target as 3 steps shown in the figure below 

<a href="https://i.stack.imgur.com/B0DrN.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/B0DrN.png" alt="enter image description here"></a>

blocks|key|326149|text|我必须确保已选中此常规测试复选框|type|unstyled|depth|inlineStyleRanges|entityRanges|data|326150|📷|atomic|offset|length|326151|​|326152|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/f1d047a41b991424f472ed8e5bddea0b.jpeg|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

I had to ensure this General Testing checkbox was set <a href="https://i.stack.imgur.com/DVMAI.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DVMAI.jpg" alt="this General Testing checkbox was set"></a>

Some code I am unit testing needs to load a resource file. It contains the following line:

<pre><code>NSString *path = [[NSBundle mainBundle] pathForResource:@"foo" ofType:@"txt"];
</code></pre>

In the app it runs just fine, but when run by the unit testing framework <code>pathForResource:</code> returns nil, meaning it could not locate <code>foo.txt</code>.

I've made sure that <code>foo.txt</code> is included in the Copy Bundle Resources build phase of the unit test target, so why can't it find the file?

Why can't code inside unit tests find bundle resources?

单元测试

文件系统

包管理器

编译器

Ubuntu

Linux

Swift

Xcode

我正在进行单元测试的一些代码需要加载资源文件。它包含以下行：NSString *path = [[NSBundle mainBundle] pathForResource:@"foo" ofType:@"txt"];在应用程序中，它运行得很好，但当由单元测试框架运行时，pathForResource:返回nil，这意味...

问为什么单元测试中的代码不能找到包资源？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么单元测试中的代码不能找到包资源？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么单元测试中的代码不能找到包资源？
EN