runIn was a bad idea

This commit is contained in:
Peter 'Pita' Martischka 2012-10-08 14:07:56 +02:00
parent 27f9906b1e
commit a4d68b2b25
2 changed files with 0 additions and 32 deletions

View File

@ -119,13 +119,6 @@ var helper = {};
return deferred;
}
helper.runIn = function($iframe, func){
var eval = $iframe.window.eval;
var funcStr = "(" + func.toString() + ")()";
return eval(funcStr);
}
/* Ensure console.log doesn't blow up in IE, ugly but ok for a test framework imho*/
window.console = window.console || {};
window.console.log = window.console.log || function(){}

View File

@ -1,29 +1,4 @@
describe("the test helper", function(){
describe("the runIn method", function(){
it("runs the function in the correct iframe", function(done){
this.timeout(5000);
helper.newPad(function(){
var chromeLength = helper.runIn(helper.padChrome$, function(){
return $("#editbar").length;
});
var outerLength = helper.runIn(helper.padOuter$, function(){
return $("#outerdocbody").length;
});
var innerLength = helper.runIn(helper.padInner$, function(){
return $("#innerdocbody").length;
});
expect(chromeLength).to.be(1);
expect(outerLength).to.be(1);
expect(innerLength).to.be(1);
done();
});
});
});
describe("the newPad method", function(){
xit("doesn't leak memory if you creates iframes over and over again", function(done){
this.timeout(100000);