Additional hooks for test fixture about js-test-driver HOT 3 CLOSED

Hi, 

I tried it a bit further: I took the Runnerquirks.html page from 
JsTestDriver.jar 
and added my special bootstrap into the head section there. This worked well so 
far. 
I further added some HTML into the body of the Runnerquirks.html file, however 
this 
is not working (it seems that the body content is reset by the framework). 

I then wrote a setUp() method in my test case where I defined the innerHTML of 
the 
body manually like this:  

TestSample.setUp = function(sTestName) {    
  document.body.innerHTML = "<div id=\"uiArea\"></div>";

  document.attachEvent("load", function() {
    var oButton = new Button("b1", {Text:"Hello"});  // "Button" is a custom widget
    setRoot("uiArea", oButton);              // "setRoot" is a function 
                                                     // from my bootstrap which is 
                                                     // setting the widget into the  
                                                     // div
  });           
};

My test function is able to access the "uiArea" div element, but not the "b1" 
Button 
widget as it is just created when the document has been loaded!

Questions: 
* Are there other ways how to define a HTML document as part of the text 
fixture? 
  Proposal: It should be possible to define an arbitrary HTML document containing 
the unit tests, get it loaded by the framework, and inject the framework JS 
files 
into the document. 
* How can widgets be tested which are rendered on the onLoad event of the 
document? 
The JSTD seems to run the unit tests already before this event is occuring. 

Best regards,
 Timo

Hi Timo,

We do not have a setUp/tearDown on the suite level.

For your other questions:
to define HTML you can use our special syntactic sugar see:
http://code.google.com/p/js-test-driver/wiki/HtmlDoc

Testing on the onload can be an issue as we are always keeping the browser hot 
and
not refreshing/reloading the page every time we run the tests. Maybe you could 
try to
run your tests in a different way?

Dropping this, as there hasn't been a response in 3 years.