… for script reloading. Began work on simple CLI for running tests on multiple browsers from the prompt. added simple test server using socket.io & express
…ally fail the testsuite, instead of going by unnoticed.
which in some browsers results in [object Object] rather than [object NodeList]. Now using duck typing for NodeList objects based on the presence of length, length being a number, presence of item method (which will be typeof string in IE and function in others, so we just check that it's not undefined) and that item(0) returns the same value as , unless it's empty, in which case item(0) will return 0, while  would return undefined. Tested in IE6, IE8, Firefox 6, Safari 5 and Chrome 16.
…ext task. Fixes #160
…odeList objects to be output as arrays This helps prevent treating any object with a length property as an array, while maintaining the ability to render NodeList objects as arrays. jsDump output tests still pass after this patch is applied.
…test cases because of internal state (config.current) being incorrectly set
…ment). * QUnit.diff: Throws exception without this if Object.prototype is set (Property 'length' of undefined. Since Object.prototype.foo doesn't have a property 'rows') * QUnit.url: Without this fix, if Object.prototype.foo is set, the url will be set to ?foo=...&the=rest. * saveGlobals: Without this fix, whenever a member is added to Object.prototype, saveGlobals will think it was a global variable in this loop. --- This time using the call method instead of obj.hasOwnProperty(key), which may fail if the object has that as it's own property (touché!). Also caching Object.prototype.hasOwn for performance and convenience, as well as toString while at it.
…se a test to fail
…/test folder once this setup actually works
…ent the semaphore more than once per call