corejavascript/typeahead.js

Travis Not running Browser tests

Open

#20 建立於 2015年10月16日

在 GitHub 查看
 (5 留言) (0 反應) (1 負責人)JavaScript (956 star) (232 fork)batch import
bughelp wanted

描述

Hi, of the 12 jobs running upon every Pull-request commit, none of the browser specific tests run!

Only the unit-test runs.

For example on #18, the tests ran, but only travis build 26.1 actually ran the test suite.

The others (browser based) had the following line in the output:

Not running any tests

which you can see for instance in travis build 26.2 and all the others in the travis build list for #18.

The line in test/ci https://github.com/corejavascript/typeahead.js/blob/master/test/ci#L5

elif [ "$TRAVIS_SECURE_ENV_VARS" == "true" -a "$TEST_SUITE" == "integration" ]; then

evaluates to

+'[' false == true -a integration == integration ']'

which must mean that "$TRAVIS_SECURE_ENV_VARS" is not set.

Who can help setting up the browser tests again?? I'd like to help but am in doubt about who has access to setting it up?

貢獻者指南

技術棧
javascript
領域
devopstesting
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Travis CI configurationbash scriptingrepository admin access
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Examine the test/ci script and the Travis CI configuration. The issue is that $TRAVIS SECURE ENV VARS is not set to true for pull requests from forks, causing the browser tests to be skipped. Check Travis CI documentation on secure environment variables and consider whether the repository requires admin intervention to set them. Look into alternative approaches that do not rely on secure vars.