Beginning with Yeti Sprint 4, Yeti will begin work on features that directly support Yahoo! Cocktails. This document details the points of integration that Yeti will support.
Yeti Sprint 4 contains two tasks for Cocktails.
These tasks fulfill this story:
A basic API will be provided that can be used by another Node.js application, e.g.
mojito test. This API will provide these features:
Yeti will require you to include its
inject.js script on the pages you're serving that contain YUI Test. You will also need to tell this script where Yeti is mounted on the server, say with a small script like
Yeti's injection script uses the following globals that should not be modified:
You will provide the configuration and routes to Yeti by
requireing Yeti into your testing CLI app. Yeti will emit an EventEmitter event when all test results arrive.
The supported flow would be to:
agentConnectevents for your use.
Implementors should be aware that Yeti follows Semantic Versioning and these features are targeted for a 0.2.0 release. Therefore, the public API and integration points provided in this sprint will change in future Yeti sprints. We are working on this together and expect changes will be needed.
Yeti Sprint 4 will not address certain error conditions that can cause browsers to disconnect from the Yeti Hub. These conditions include but are not limited to:
In these cases, Yeti may fail. For this sprint, implementors must take care that their tests are well-formed. Handling these kinds of errors is in Yeti's task backlog.
Yeti Sprint 4 does not let you pick which browsers to use. This feature is in Yeti's backlog.
Instead, use any number of Selenium or WebDriver client libraries to handle browser opening and closing to the Yeti capture page.
Yeti requires Node.js
>=0.6.0 <0.7.0 and is being developed against Node.js 0.6.10.
Read: Yeti is not yet tested on Windows, but we are interested in Windows support for the future.
These tasks have been asked for by Cocktails, but they are not being promised for Sprint 4.
window.onerrorcollisions on test pages.
This section and the linked articles are non-normative.