adding jasmine test adapter
Accepting all positive HTTP status

201 is as good as 200 :-)
Propagating the HTTP status code for success as well.
Using sinon.xhr to fake XHR response status code.

ISO tests for the moment.
Adding tests for 202 response and 300 response.
Extracted the modifiers array into a function, as the same array literal appeared in the tests 21 times
Replaced queue.call test with an awful Jasmine adapter compatible version
Replaced queue.call test with Jasmine-adapter friendly assertions. Rather than repeat a great deal of set-up in a second awful test the extra assertions have been added to the first.
Updated @link content to not be potentially encoded.
Resolving fix-now issues from queue.call conversion code review by John B:

* Mocking require needed comments for clarity
* Exiting potentially infinite loop with test failure to avoid spinlock
* Tabbing fix.
* Constants for magic values around animation duration and onComplete calling
Remove Sinon fake timers from test after refactoring

Fake timers were added after refactoring to remove queue.call() from
the CSS3 tests. However, the fake timers have no bearing on the test.
The property changes being tested are set synchronously.
Refactored out the whole config into a function, with logging level and logging strategy set with parameters.
Merge branch 'master' of https://github.com/fmtvp/tal
Merge branch 'master' into TVPJSFRMWK-1741
Updated list of files containing tests, commenting out ones that are causing TypeErrors and seem to be affecting other tests. FIXME added
Resolved two groups of ReferenceErrors
Removed jstestdriver.console.log messages (as this is unsupported in the Jasmine adaptor) and removed files that only contained references to such. Added cehtml media modifier to the set of those commented out from the spec runner as it now causes type errors.
Corrected remaining ReferenceError for current test set
JSTestDriver's assertExpection has an optional third argument specifying the expected error; allow this syntax through the adapater (even if it's not checked)
RunTimeContext tests were not cleaning up after themselves, leading to subsequent tests failing. Clean-up coded added.