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.
Travis Not running Browser tests · corejavascript/typeahead.js#20 | Good First Issue