Use test.ini when building test extensions
Using development.ini to test extension builds isn't ideal, because basemodel.create_all is set to True, which attempts to contact ElasticSearch, which isn't running on Travis.

Using development.ini to test extension builds isn't ideal, because basemodel.create_all is set to True, which attempts to contact ElasticSearch, which isn't running on Travis.
hypothesis
Unified Split

Showing with 10 additions and 3 deletions.

+2 −2 .travis.yml

+8 −1 conf/test.ini
diff --git a/.travis.yml b/.travis.yml
@@ -15,8 +15,8 @@ script:
  - make test
  - make cover
  - make lint
-  - hypothesis-buildext conf/development.ini chrome --base http://localhost
-  - hypothesis-buildext conf/development.ini firefox --base http://localhost
+  - hypothesis-buildext conf/test.ini chrome --base http://localhost
+  - hypothesis-buildext conf/test.ini firefox --base http://localhost
  - "hypothesis-buildext conf/production.ini chrome
    --base https://hypothes.is
    --assets chrome-extension://notarealkey/public"
diff --git a/conf/test.ini b/conf/test.ini
@@ -3,6 +3,12 @@ use: egg:h

 es.host: http://localhost:9200

+h.feature.accounts: True
+h.feature.api: True
+h.feature.claim: True
+h.feature.streamer: True
+h.feature.notification: True
+
 sqlalchemy.url: sqlite://

 webassets.base_dir: h:static
@@ -14,7 +20,8 @@ webassets.manifest: False
 webassets.static_view: True
 webassets.uglifyjs_bin: node_modules/.bin/uglifyjs
 webassets.cleancss_bin: node_modules/.bin/cleancss
-webassets.coffee_bin: node_modules/.bin/coffee
+webassets.browserify_pipe_bin: bin/browserify-pipe
+

 [loggers]
 keys = root, h