Tags: rajeshvv/yui3
Tags
Merge branch 'template' into 3.x Conflicts: build/loader-yui3/loader-yui3-coverage.js build/loader-yui3/loader-yui3-debug.js build/loader-yui3/loader-yui3-min.js build/loader-yui3/loader-yui3.js build/loader/loader-debug.js build/loader/loader-min.js build/loader/loader.js build/simpleyui/simpleyui-min.js build/yui-base/yui-base-coverage.js build/yui-base/yui-base-min.js build/yui-core/yui-core-coverage.js build/yui-core/yui-core-min.js build/yui-nodejs/yui-nodejs-coverage.js build/yui-nodejs/yui-nodejs-debug.js build/yui-nodejs/yui-nodejs-min.js build/yui-nodejs/yui-nodejs.js build/yui/yui-coverage.js build/yui/yui-debug.js build/yui/yui-min.js build/yui/yui.js src/loader/js/yui3.js
Add .yeti.json to set project basedir and glob. The basedir setting makes sure any use of Yeti inside the project serves your `src` and `build` directories to the Yeti Hub and therefore the browsers running the tests. The glob definition is not perfect: the `src/yui` directory contains files that match the glob but are not always desired for testing. It is otherwise a suitable default. http://yeti.cx/docs/v0.2.12/quick-start/#Configuration-file Note: if you are already using a project-level .yeti.json to always use a remote Hub, please copy your current .yeti.json to your home directory. Yeti will consider both your home directory's settings and the project's configuration files when setting defaults, but the project's settings take precedence.
PreviousNext