Approval Tests are an alternative to assertions. You’ll find them useful for testing objects with complex values (such as long strings), lots of properties, or collections of objects.
ApprovalTests.Swift is compatible with the XCTest testing framework.
We’ll start by writing a simple unit test to verify a list of names. But instead of using XCTest’s XCTAssertEqual function, we’ll use Approvals.verifyAll:
The verifyAll() function performs a test assertion for a list of items. Unlike a normal assertion, it doesn’t specify an expected list. Instead, this will produce a “received” file matching the name of your test suite and test case. In this example, it will write a file SampleArrayTests.testList.received.txt:
[0] = Dan
[1] = James
[2] = Jason
[3] = Katrina
[4] = Llewellyn
It also opens two files in a diff editor—the “received” file, and the “approved” file.
To approve the results, tell the diff editor to apply changes from the left side to the right side:
Most of the time, you’ll use one of the supported diff tools to examine and approve the result. If you don’t have any of these diff tools, you can rename the received file to SampleArrayTests.testList.approved.txt and the test will now pass.
Getting Started
The best way to get started is download and open one of the starter projects:
These are standard projects and can be imported into any editor or IDE. They also all have CI with Github actions.
They come ready with:
A Swift package definition adding ApprovalTests.Swift to the test target
A suitable .gitignore to exclude approval artifacts
A GitHub action to build and run tests
A GitHub build status badge
Predefined Verifiers
ApprovalTests.Swift comes with useful verifiers:
Approvals.verify — verify object or dictionary
Approvals.verifyAll — verify array of items (or use array as inputs)
Approvals.verifyAsJSON — verify Encodable object converted to JSON
Approvals.verifyQuery — verify query, also showing query results on failure
Approvals.verifySequence — verify sequence of changing values
How to Use with iOS
ApprovalTests.Swift runs out-of-the-box for macOS tests. But for iOS tests, you need a separate process running on your Mac to watch for diffs. Run iOSApprovalsWatcher.py from your command line, giving it the path to your test directory.
Which File Artifacts to Exclude from Source Control
You must add any “approved” files to your source control system. But “received” files can change with any run and should be ignored. For Git, add this to your .gitignore:
*.received.*
If you have iOS tests, you should also add command.sh to your .gitignore. (They are scripts written by the iOS side for the file monitor to execute from the macOS side.) So for iOS testing, make sure to exclude:
Then drag the the built framework from the appropriate Carthage/Build directory into your project,
but with “Copy items into destination group’s folder” disabled.
CocoaPods
If you want to add ApprovalTests.Swift using Cocoapods then add the following dependency to your Podfile.
Most people will want ApprovalTests.Swift in their test targets, and not include any pods from their main
targets:
target 'MyTests' do
inherit! :search_paths
use_frameworks!
pod 'ApprovalTests_Swift', '~> 2.0'
end
Approval Tests are an alternative to assertions. You’ll find them useful for testing objects with complex values (such as long strings), lots of properties, or collections of objects.
ApprovalTests.Swift is compatible with the XCTest testing framework.
Contents
My First Approval Test
We’ll start by writing a simple unit test to verify a list of names. But instead of using XCTest’s
XCTAssertEqual
function, we’ll useApprovals.verifyAll
:snippet source | anchor
The
verifyAll()
function performs a test assertion for a list of items. Unlike a normal assertion, it doesn’t specify an expected list. Instead, this will produce a “received” file matching the name of your test suite and test case. In this example, it will write a fileSampleArrayTests.testList.received.txt
:snippet source | anchor
It also opens two files in a diff editor—the “received” file, and the “approved” file.
To approve the results, tell the diff editor to apply changes from the left side to the right side:
Most of the time, you’ll use one of the supported diff tools to examine and approve the result. If you don’t have any of these diff tools, you can rename the received file to
SampleArrayTests.testList.approved.txt
and the test will now pass.Getting Started
The best way to get started is download and open one of the starter projects:
These are standard projects and can be imported into any editor or IDE.
They also all have CI with Github actions.
They come ready with:
.gitignore
to exclude approval artifactsPredefined Verifiers
ApprovalTests.Swift comes with useful verifiers:
Approvals.verify
— verify object or dictionaryApprovals.verifyAll
— verify array of items (or use array as inputs)Approvals.verifyAsJSON
— verify Encodable object converted to JSONApprovals.verifyQuery
— verify query, also showing query results on failureApprovals.verifySequence
— verify sequence of changing valuesHow to Use with iOS
ApprovalTests.Swift runs out-of-the-box for macOS tests. But for iOS tests, you need a separate process running on your Mac to watch for diffs. Run iOSApprovalsWatcher.py from your command line, giving it the path to your test directory.
Which File Artifacts to Exclude from Source Control
You must add any “approved” files to your source control system. But “received” files can change with any run and should be ignored. For Git, add this to your
.gitignore
:If you have iOS tests, you should also add
command.sh
to your.gitignore
. (They are scripts written by the iOS side for the file monitor to execute from the macOS side.) So for iOS testing, make sure to exclude:Other Ways to Get It
Swift Package Manager
See an example package manifest here
Get the following dependency:
anchor
Then add it to your test target:
anchor
Carthage
Add the following to your Cartfile:
Then drag the the built framework from the appropriate Carthage/Build directory into your project, but with “Copy items into destination group’s folder” disabled.
CocoaPods
If you want to add ApprovalTests.Swift using Cocoapods then add the following dependency to your Podfile. Most people will want ApprovalTests.Swift in their test targets, and not include any pods from their main targets:
For More Information
Questions?
Ask Llewellyn Falco @LlewellynFalco or Jon Reid @qcoding on Twitter.
Documentation
Find some extra documentation here.
Video Tutorials
You can also watch a series of short videos about using ApprovalTests in .Net on YouTube.
Podcasts
Prefer learning by listening? Then you might enjoy the following podcasts: