jQuery Forum

How am I currently affected by this?  I’m using sinon in conjunction with QUnit, and am trying to clean up my spys and stubs in a teardown function.  The problem is that if the teardown callback of the first test hasn’t run before the second test begins then the sinon sandbox will not have been cleaned up.  Here’s a snippet of this in action:

1. define(["myclass", "mydependency", "qunit", "sinon", "sinonqunit"], function (myclass, mydependency, QUnit, sinon) {
2.  
3.     var run = function() {
4.  
5.         var sandbox;
6.         module("myclass", {
7.             setup: function() {
8.                 sandbox = sinon.sandbox.create();
9.             },
10.             teardown: function() {
11.                 sandbox.restore();
12.             }
13.         });
14.  
15.         test("doSomething calls someFunction on mydependency", function() {
16.             // Arrange
17.             var spy = sinon.spy(mydependency, "someFunction");
18.            
19.             // Act
20.             myclass.doSomething(mydependency);
21.  
22.             // Assert
23.             ok(spy.calledOnce);
24.         });
25.        
26.         test("doSomethingElse calls someOtherFunction on mydependency", function () {
27.             // Arrange
28.             var spy = sinon.spy(mydependency, "someOtherFunction");
29.  
30.             // Act
31.             myclass.doSomethingElse(mydependency);
32.  
33.             // Assert
34.             ok(spy.calledOnce);
35.         });
36.     };
37.  
38.     return { run: run };
39. });

Is this an issue with QUnit or am I doing something silly?  Comparing this with .NET - both nunit and mstest keep their setup and teardown functions atomic with the test itself.