Yeti

Developed for Yahoo, Yeti starts unit tests via the Node.js console, opening browser mocking toolkits like Selenium, running the tests, and then reporting on the results back in the console.

Yeti can work with tests written in various testing frameworks like YUI Test, Jasmine, QUnit, Mocha, and many more.

Because of this tight Selenium integration, Yeti is the perfect tool for testing JS code and how it renders not only in an agnostic environment, but in different browsers and OS platforms, even mobile.

For this same reason Yeti was developed by Yahoo, being still used today to test Yahoo products on various devices and browsers before their launch.

What is new in this release:

• Yeti 0.2.27 provides first-class code coverage reporting provided by Istanbul.
• Excluding files from instrumentation.
• Prefer --caps for browser launching.

What is new in version 0.2.24:

• Report root cause of Selenium/WebDriver errors that occur during browser launching.
• Allow WINDOWS as a platform name in the --browser launch option for Selenium.
• Add new Sauce Labs platform names: Windows XP, Windows 7, Windows 8, OS X 10.6, and OS X 10.8.
• Add Client-Side Yeti Integration (Generic Driver) for using Yeti to automate other frameworks.
• Add --name option to label JUnit XML tests for display in Jenkins merged test reports.

What is new in version 0.2.22:

• Automatically restart stalled browsers when using WebDriver.
• Avoid Selenium proxy in Sauce Labs to support IE 6-9.
• Sauce Labs maximum duration is set by Yeti to 2 hours.
• Support for HTTP_PROXY and HTTPS_PROXY environment variables when installing Yeti dependencies.
• Crash fix: prevent calling _launch twice when starting a browser.
• Crash fix: properly close duplicate connection.

What is new in version 0.2.21:

• Accept latest as a WebDriver browser version.
• Add browsers used by Sauce Labs.
• Fix server-side wd-url command-line option.
• Fix issue with echoecho JSONP when using a query string like &callback=foo.
• Fix possible hang during WebDriver browser launching.
• Fix possible quit before JUnit XML was completely writted to stdout.

What is new in version 0.2.14:

• Removed NFE for IE8 support.
• New instances of a browser already in a Batch can join the Batch.
• Prevent zombie browser errors.
• Do not allow more than 1 socket with the same Agent ID.
• False CLI test failure when ran offline.

What is new in version 0.2.13:

• Added AJAX testing routes provided by echoecho.
• Added basic support for QUnit.
• New error event for non-essential 404s, omitted by the CLI.
• Feedback line clears before test results for cleaner output.
• Improved feedback line reporter time formatting.
• socketWrite crash after end().
• Browser test driver rewrite using YUI.

What is new in version 0.2.12:

• Fixes:
• Introduce --junit option to output JUnit XML.
• --hub option properly accepts urls and Booleans.
• Resolved a flaky event test race condition.
• Prevent crashes from malformed Yeti RPC calls.

What is new in version 0.1.0:

• Report full User-agent string.
• Corrected dependency versions in package.json.
• Minor enhancements for future releases.

Requirements:

• Node.js 0.8 or higher