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-5Lines changed: 3 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Xcode Project Setup
9
9
Before you get started, there are a couple of steps you will need to take to prepare your project:
10
10
11
11
1. Depending on your version of Xcode, you may need to get Xcode's coverage instrumentation by going to Xcode > Preferences, into Downloads, and installing Command Line Tools. If you do not see this as an option in the Downloads section, the tools should already be installed.
12
-
4. In your Xcode project, enable these two build settings at the project level for your Debug configuration only:
12
+
2. In your Xcode project, enable these two build settings at the project level for your Debug configuration only:
13
13
* Instrument Program Flow
14
14
* Generate Test Coverage Files
15
15
@@ -19,7 +19,7 @@ Installation: Standard
19
19
20
20
1. Fork this repository; you're probably going to want to make your own modifications.
21
21
2. Place the XcodeCoverage folder in the same folder as your Xcode project.
22
-
5. In your main target, add a Run Script build phase to execute `XcodeCoverage/exportenv.sh`
22
+
3. In your main target, add a Run Script build phase to execute `XcodeCoverage/exportenv.sh`
23
23
24
24
A few people have been tripped up by the last step: Make sure you add the script to your main target (your app or library), not your test target.
25
25
@@ -65,10 +65,8 @@ If you make changes to your production code, you should clear out all build arti
65
65
Modification
66
66
============
67
67
68
-
There are two places you may want to modify the included files if you are using the standard installation:
68
+
If you are using the standard installation, you may wish to modify `exclude_data()` in `getcov` to specify which files to exclude, for example, third-party libraries.
69
69
70
-
1. In `envcov.sh`, `LCOV_INFO` determines the name shown in the report.
71
-
2. In `getcov`, edit `exclude_data()` to specify which files to exclude, for example, third-party libraries.
0 commit comments