Front-End Unit Tests failing on first two tests

[jbonacci]

Not a good precedent to set - having the first two unit tests fail!
Found on all browsers after a local install...

Details:
Tests completed in 105838 milliseconds.
967 tests of 969 passed, 2 failed.

1. include.js: navigator.id is available (1, 0, 1)Rerun

   navigator.id namespace is available
   Expected:

   "object"

   Result:

   "undefined"

   Diff:

   "object" "undefined"

   Source:

   ()@http://127.0.0.1:10002/test/qunit/qunit.js:102

2. include.js: navigator.id.getVerifiedEmail is available (1, 0, 1)Rerun

   Died on test Client should remember what ids you use #1: navigator.id is undefined - { "fileName": "http://127.0.0.1:10002/test/cases/include.js", "lineNumber": 16 }

As a side note, look at that completion time!
Twice normal!

[jbonacci]

Ah, so the delay is from the running/failing of the first two tests.

Here is what the failures look like from a "headless" run:
Test navigator.id.getVerifiedEmail is available died, exception and test follows
TypeError: Result of expression 'navigator.id' [undefined] is not an object.
function () {
equal(typeof navigator.id.getVerifiedEmail, "function", "navigator.id.getVerifiedEmail is available");
}
'waitFor()' finished in 63434ms.

Test name (failed, passed, total)

include.js: navigator.id is available (1, 0, 1)Rerun
navigator.id namespace is available
Expected:
"object"
Result:
"undefined"
Diff:
"object" "undefined"

include.js: navigator.id.getVerifiedEmail is available (1, 0, 1)Rerun
Died on test #1: Result of expression 'navigator.id' [undefined] is not an object. - { "message": "Result of expression 'navigator.id' [undefined] is not an object.", "line": 16, "sourceId": 168486280, "sourceURL": "http://127.0.0.1:10002/test/cases/include.js", "expressionBeginOffset": 638, "expressionCaretOffset": 650, "expressionEndOffset": 667, "name": "TypeError" }

[shane-tomlinson]

@jbonacci - unable to reproduce. This looks like your include.js file is not being found, which leads me to believe there is a build script problem or your include.js is not being served from the directory it should be.

Can you confirm in Firebug or Chrome Dev Tools and see if there is a 404 for include.js?

If this is the problem, we have to fix the build script.

[jbonacci]

Verified as fixed, but now see #1042.