DOH tearDown not working as expected

[jimvorbau]

When running a doh test, the tearDown function of a test will not be called if the test is unsuccessful.

This is very unlike most testing frameworks. setUp should always be called before a test and tearDown after. That way, things like the state of the HTML, etc., can be reset for the next test.

In runner.js, doh._runFixture calls tearDown at the end of a try statement. This line of code shold really go in a finally block.

Here is a suggested change. Change this snippet:

  if(fixture["tearDown"]){ fixture.tearDown(this); }
 }catch(e){
  threw = true;
  err = e;
  if(!fixture.endTime){
   fixture.endTime = new Date();
  }
 }

to this:

 }catch(e){
  threw = true;
  err = e;
  if(!fixture.endTime){
   fixture.endTime = new Date();
  }
 }
finally {
if(fixture["tearDown"]){ fixture.tearDown(this); }
}

[bill]

Make sense.

tearDown() doesn't even get called when the test gets an error because a doh.is(), doh.t() etc. assertion failed?

[jimvorbau]

Correct, tearDown() doesn't get called if there is a test failure caused by a normal doh.is() assertion.

[haysmark]

In [28985]:

tearDown should be called regardless of the test's outcome. Fixes #12487. !strict

[bill]

[28985] completely hangs runTest.html.

Tested via dijit/tests/runTest.html on IE8. util/doh/runner.html?testModule=dijit.tests._base.module also hangs.

[haysmark]

In [29040]:

Don't call tearDown in async case (it is called much later). Added new test cases demonstrating problem with tearDown for failing sync tests. Fixes #12487. !strict