test: fix setTimeout in testing environment

The test runner wraps `setTimeout` and `setInterval`, figuring that 
you'll advance time manually, but that's not what our tests expect. 
Luckily, it can be turned off.

Author: savetheclocktower

spec/node-path-tester-spec.js

@@ -1,4 +1,5 @@
 'use babel';
+/* global pass */
 
 import NodePathTester from '../lib/node-path-tester';
 
@@ -26,10 +27,9 @@ describe('Node path tester', () => {
       expect(await NodePathTester.test('node')).not.toBe(false);
       try {
         await NodePathTester.test('fdsfljksdafd');
-        // If we get this far, fail the test
-        expect(false).toBe(true);
+        fail();
       } catch (err) {
-        expect(err instanceof Error).toBe(true);
+        pass();
       }
     });
   });

spec/runner.js

@@ -16,7 +16,21 @@ function setDefaultSettings(namespace, settings) {
 module.exports = createRunner({
   testPackages: ['linter', 'linter-ui-default'],
   timeReporter: true,
-  specHelper: true
+  specHelper: {
+    atom: true,
+    attachToDom: true,
+    ci: true,
+    customMatchers: true,
+    jasmineFocused: true,
+    jasmineJson: true,
+    jasminePass: true,
+    jasmineTagged: true,
+    mockClock: true,
+    mockLocalStorage: true,
+    profile: true,
+    set: true,
+    unspy: true
+  }
 },
 () => {
   beforeEach(() => {