Amend the README to avoid a bug in Xcode 5.1. (closes #154)
Merge pull request #155 from inkling/jeff/xcconfig_crash

Amend the README to avoid a bug in Xcode 5.1. (closes #154)
Increment the instruments retry loop counter _after_ it's used.

Previously, we'd skip the first value of the launch timeouts array (30)
and then use a value beyond the array's length, as can be seen in
https://travis-ci.org/inkling/Subliminal/jobs/21707856.
Cut down README
Add the ability to order tests by run group.

See the documentation on `+[SLTest runGroup]`.
Add Usage and CI sections based on Jeff's suggestions [ci skip]
Add link to comparison section and other guides in the wiki in the How to Get Started section section
Add Podspec
Merge pull request #160 from MaxGabriel/slimREADME

Cut down README
Pick up the latest OCMock to resolve Xcode 5.1. warnings.
Merge pull request #165 from inkling/jeff/pick_up_ocmock

Pick up the latest OCMock to resolve Xcode 5.1. warnings.
Merge pull request #30 from MaxGabriel/cleanCocoapod

Add Podspec
Use dispatch_get_specific to workaround the deprecation of dispatch_get_current_queue.
Merge pull request #168 from MaxGabriel/dispatchGetCurrentQueue

Use dispatch_get_specific to workaround the deprecation of dispatch_get_current_queue
Merge pull request #156 from inkling/jeff/correct_instruments_retry_count

Increment the instruments retry loop counter _after_ it's used.
Cast to NSURL to silence warning when using Cocoapods
Merge pull request #170 from MaxGabriel/castToURL

Cast to NSURL to silence warning when using Cocoapods
Remove TRAVIS environment variable from .travis.yml
Merge pull request #172 from MaxGabriel/patch-3

Remove TRAVIS environment variable from .travis.yml
Allocate pixels with all zero components for bitmap context

We should use calloc here instead of malloc to ensure that the
pixel buffer we use for testing visibility is all clear when
nothing has been drawn yet.  This can be an issue in cases where
renderViewRecursively doesn't actually draw anything.  If nothing
is drawn then this function should return 0, but if we're unlucky
with the random values in the malloced pixel buffer we might see
something "drawn" in the pixel buffer anyway and return non-zero.