Yeti 0.2.7 released
Today I’m releasing Yeti 0.2.7, which correctly returns connected browsers to the capture page if you decide to cancel a test run. This is really useful when you notice test failures and want to save time by canceling before the batch is complete.
You can install the latest Yeti with one command:
npm install -g yeti
Parallel testing coming soon
Yeti 0.2.7 prefers to identify browsers by the Agent ID in the URL instead of by cookies.
This lets a single browser instance connect to Yeti multiple times. This isn’t very useful yet, but it will allow for future Yeti releases to treat each captured tab or window as a group and split the test workload among all of the tabs.
We here at YUI plan to include Yeti in our Travis CI testing; however, testing our GBS baseline browsers takes longer than Travis' 10 minute time limit. Therefore, we plan to start many instances of these browsers across VMs that will split the load and run our CI tests faster than ever before.
Stay tuned for these features and more in upcoming releases.
General documentation: http://yeti.cx/docs/v0.2.7/quick-start/
API documentation: http://yeti.cx/docs/v0.2.7/api/
Detailed API documentation: http://yeti.cx/docs/v0.2.7/api/everything/
CI testing: http://travis-ci.org/yui/yeti
Code coverage: http://yeti.cx/docs/v0.2.7/coverage.html
Report a bug: http://yuilibrary.com/projects/yeti/newticket