You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-30
Original file line number
Diff line number
Diff line change
@@ -128,12 +128,12 @@ If your data can be represented as an image, text, or data, you can write a snap
128
128
129
129
## Installation
130
130
131
-
### Xcode 11
131
+
### Xcode
132
132
133
133
> ⚠️ Warning: By default, Xcode will try to add the SnapshotTesting package to your project's main application/framework target. Please ensure that SnapshotTesting is added to a _test_ target instead, as documented in the last step, below.
134
134
135
135
1. From the **File** menu, navigate through **Swift Packages** and select **Add Package Dependency…**.
136
-
2. Enter package repository URL: `https://github.com/pointfreeco/swift-snapshot-testing.git`
136
+
2. Enter package repository URL: `https://github.com/pointfreeco/swift-snapshot-testing`
137
137
3. Confirm the version and let Xcode resolve the package
138
138
4. On the final dialog, update SnapshotTesting's **Add to Target** column to a test target that will contain snapshot tests (if you have more than one test target, you can later add SnapshotTesting to them by manually linking the library in its build phase)
139
139
@@ -144,7 +144,7 @@ If you want to use SnapshotTesting in any other project that uses [SwiftPM](http
> ⚠️ Warning: Carthage instructs you to drag frameworks into your Xcode project. Xcode may automatically attempt to link these frameworks to your app target. `SnapshotTesting.framework` is only compatible with test targets, so when you first add it to your project:
177
-
>
178
-
> 1. Remove `SnapshotTesting.framework` from any non-test target it may have been added to.
179
-
> 2. Add `SnapshotTesting.framework` to any applicable test targets.
180
-
> 3. Add a **New Copy Build Phase** to any applicable test targets with **Destination** set to "Frameworks", and add `SnapshotTesting.framework` as an item to this phase.
181
-
> 4. Do _not_ add `SnapshotTesting.framework` to the "Input Files" or "Output Files" of your app target's Carthage `copy-frameworks`**Run Script Phase**.
182
-
>
183
-
> See Carthage's "[Adding frameworks to unit tests or a framework](https://github.com/Carthage/Carthage#adding-frameworks-to-unit-tests-or-a-framework)" documentation for more.
184
-
185
-
### CocoaPods
186
-
187
-
If your project uses [CocoaPods](https://cocoapods.org), add the pod to any applicable test targets in your `Podfile`:
188
-
189
-
```ruby
190
-
target 'MyAppTests'do
191
-
pod 'SnapshotTesting', '~> 1.9.0'
192
-
end
193
-
```
194
-
195
168
## Features
196
169
197
170
-[**Dozens of snapshot strategies**](Documentation/Available-Snapshot-Strategies.md). Snapshot testing isn't just for `UIView`s and `CALayer`s. Write snapshots against _any_ value.
0 commit comments