Skip to content

Commit 34cd747

Browse files
committed
Update README.md
1 parent f606d8a commit 34cd747

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Alcove [![Build Status](https://travis-ci.org/ioveracker/Alcove.svg?branch=master)](https://travis-ci.org/ioveracker/Alcove)
1+
# Alcove [![Gem Version](https://badge.fury.io/rb/alcove.svg)](http://badge.fury.io/rb/alcove) [![Build Status](https://travis-ci.org/ioveracker/Alcove.svg?branch=master)](https://travis-ci.org/ioveracker/Alcove)
22
Painless code coverage reporting for Objective-C projects. Most of the heavy lifting is done by the venerable lcov. Alcove simply searches the nooks and crannies to collect the data needed to generate the report and ties everything together for you. Best of all, it's a gem with minimal depedencies, so installation is quick and painless.
33

44
## Installation
@@ -16,7 +16,8 @@ If you don't have it already, you'll also need to install lcov.
1616
$ sudo port install lcov
1717

1818
## Xcode Project Configuration
19-
If you haven't already, open your project in Xcode and update your main target to Generate Test Coverage Files and Instrument Program Flow *for Debug configuration only*).
19+
If you haven't already, open your project in Xcode and update your non-test targets to Generate Test Coverage Files and Instrument Program Flow *for Debug configuration only*).
20+
![Xcode](http://i.imgur.com/xdcg4er.png?1)
2021

2122
## Generating Reports
2223
Now that you have the prerequisites out of the way, you can generate a report. Make sure you've recently executed your tests, then:

0 commit comments

Comments
 (0)