update to version from npm-lockdown@0.0.5. Fixes #3303
upgrade to qunit 1.12.0 from git sha a115f28 on git://github.com/jquery/qunit.git
assert affirmatively that the previous line did not throw
temporarily remove lloyd on this branch
expect(0): neither the error nor success callbacks below should fire in this test
expect(0): we only assert on failure is this asyncTest callback
expect(0): we only assert when called unexpectedly
Run a no-op test to satisfy QUnit requirement that tests must have at least one assertion
Use the relative luminance function provided by the W3C to determine whether to show the light or dark text.
* Use white or black text only.
Cleanup of the foreground color changes.

* Update the tests
* Instead of setting the foreground-color manually, use CSS w/ .light & .dark classes.
* Rename foregroundColor to foregroundColorClass

fixes #3725
More cleanup:

* Remove calculate from function names
* Pass rgb colors as an object with named keys instead of an array.
Merge pull request #3837 from mozilla/issue_3725-color-clash

Issue 3725 color clash

@callahad is sat next to me. He gives me the r+
Merge pull request #3796 from jrgm/update-lockdown-to-pass-down-full-env

update ./scripts/lockdown to version from npm-lockdown@0.0.5. Fixes #3303

@jrgm - I have no problem with this PR to progress on the road to fixing #3303.
Fix up the tests!

* Fix the broken redirect test to actually test something appropriate - like the redirect works.
* Stop all modules between the test runs.
* Make sure the module mock has a stop function and no exceptions are thrown.
* Make sure that primary_user_provisioned.js calls the ready function on success.
* If currently unable to test focus, assert true so QUnit does not complain.
match /Tests completed in \d+ milliseconds/ for test completion
document changes in train-2013.08.28
bump version in dev after branching train-2013.08.28
Merge pull request #3839 from mozilla/qunit-update

Qunit update

@jrgm - I manually tested that this fixes #3797 by manually adding a `throw new Error("random error");` outside of any tests to see if the error is caught and displayed as a failure. It is. All other tests run as expected. Tests are happy in Firefox, Chrome, Safari, Opera, and run in IE8 with already known about failures.

r+

fixes #3797
email_hint - initial sketch
use hint to pre-fill email address in dialog