Relative path to inject.js in jqunit not guaranteed outside of infusion
Description
collectionspace has a different directory structure for their test framework than infusion uses. They are making use of infusions code, which results in the path to inject.js being incorrect in jqunit.js.
Environment
None
Activity
Show:
Justin Obara July 14, 2014 at 2:28 PM
We no longer use testswarm and this file has been removed.
Justin Obara June 22, 2010 at 6:32 PM
using windows.location doesn't work either as it uses the window.location from the iframe instead of from the parent page.
Justin Obara June 22, 2010 at 11:51 AM
The testswarm server also hosts a copy of the inject.js script. Now pointing at that version of the file instead of distributing one in the source code.
Justin Obara June 21, 2010 at 3:28 PM
This actually didn't work. the path was specified relative to the js file instead of the html file it gets injected into
Justin Obara June 17, 2010 at 6:46 PM
Moved the entire testswarm directory from the lib directory to the jqunit directory
collectionspace has a different directory structure for their test framework than infusion uses. They are making use of infusions code, which results in the path to inject.js being incorrect in jqunit.js.