FLUID-3673: Relative path to inject.js in jqunit not guaranteed outside of infusion

Metadata

Source
FLUID-3673
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Justin Obara
Reporter
Justin Obara
Created
2010-06-17T14:38:37.984-0400
Updated
2014-07-30T15:29:17.131-0400
Versions
  1. 1.4
Fixed Versions
  1. 1.5
Component
  1. Testing Infrastructure

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.

Comments

  • Justin Obara commented 2010-06-17T14:46:54.895-0400

    Moved the entire testswarm directory from the lib directory to the jqunit directory

  • Justin Obara commented 2010-06-21T11:28:16.555-0400

    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 commented 2010-06-22T07:51:07.434-0400

    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 commented 2010-06-22T14:32:43.487-0400

    using windows.location doesn't work either as it uses the window.location from the iframe instead of from the parent page.

  • Justin Obara commented 2014-07-14T10:28:19.183-0400

    We no longer use testswarm and this file has been removed.