Update README

README.md

@@ -1,4 +1,4 @@
-# OpenAerialMap Frontend
+# OpenAerialMap Frontend [![Build Status](https://travis-ci.org/hotosm/oam-browser.svg?branch=develop)](https://travis-ci.org/hotosm/oam-browser) ![BrowserStack Status](https://www.browserstack.com/automate/badge.svg?badge_key=cXlaWlgyeEhmUUlISEpjTU9OQTg3RzdLVUlqUWo0V0JsOG5sMGJ4MlNnYz0tLWhtNFRWMnBlYWJnQUd6TFFZVzJxK3c9PQ==--955a5de2e9ea1506cdeb8cebdcbca07435613863)
 
 OpenAerialMap (OAM) is a set of tools for searching, sharing, and using openly licensed satellite and unmanned aerial vehicle (UAV) imagery.
 
@@ -19,6 +19,8 @@ yarn start
 
 You should be able to see the site in your browser at `http://localhost:3000`
 
+However, to get all functionality you will also need to point it at a running [Catalog API](https://github.com/hotosm/oam-catalog). By default the endpoint of the staging instance of the API will be used, however you can change the endpoint to a locally running API in `src/config/local.js`.
+
 ## Deployment
 
 This is a Single Page Application and needs only a web server to serve it. Therefore it can be hosted on S3 or just
@@ -40,11 +42,13 @@ These should be isolated and fast, with as much mocking/stubbing as possible, su
 `mocha --opts test/specs/mocha.opts test/specs` or `npm test`
 
 **Integration tests**, under `test/integration`    
-These are end-to-end, cross-browser tests, that should test as much of the stack as possible. Currently they are run on Browser Stack against various browsers. They can be run locally against a Web Driver compatible browser client like (chromedriver)[https://sites.google.com/a/chromium.org/chromedriver/] or (geckodriver)[https://github.com/mozilla/geckodriver]. 
+These are end-to-end, cross-browser tests, that should test as much of the stack as possible. Currently they are run on Browser Stack against various browsers. They can be run locally against a Web Driver compatible browser client like [chromedriver](https://sites.google.com/a/chromium.org/chromedriver/) or [geckodriver](https://github.com/mozilla/geckodriver). 
 You will need a running [Catalog API](https://github.com/hotosm/oam-catalog), the repo has a Dockerfile to quickly get
 a local version of the API running. Then you can run tests with;
 `wdio test/integration/wdio.local.conf.js`.
 
+Note that Browserstack tests both a pinned version of the API (defined in `package.json` and the latest version of the API).
+
 Because `wdio` wraps `mocha`, you can send `mocha` args via `wdio.default.conf.js`'s `mochaOpts` field. For instance `grep` has been added so you can isolate a single test run with:    
 `MOCHA_MATCH='should find imagery' wdio test/integration/wdio.local.conf.js`