Fixing "flaky" js tests: when spying on teardown and not calling it through we were ending up with a component in memory that was blowing up the next tests

1 files changed, 2 insertions, 2 deletions

diff --git a/web-ui/test/spec/tags/ui/tag_shortcut.spec.js b/web-ui/test/spec/tags/ui/tag_shortcut.spec.js
index ba44304e..862e0d1c 100644
--- a/web-ui/test/spec/tags/ui/tag_shortcut.spec.js
+++ b/web-ui/test/spec/tags/ui/tag_shortcut.spec.js
@@ -42,8 +42,8 @@ describeComponent("tags/ui/tag_shortcut", function () {
     var shortcutAddedAfterEmptyingParent = TagShortcut.appendedTo(parent, { linkTo: { name: 'inbox', counts: { total: 15 }}, trigger: component });
     // by now shorcut is not in the DOM anymore but shortcutAddedAfterEmptyingParent is
 
-    spyOn(shortcut, 'teardown');
-    spyOn(shortcutAddedAfterEmptyingParent, 'teardown');
+    spyOn(shortcut, 'teardown').andCallThrough();
+    spyOn(shortcutAddedAfterEmptyingParent, 'teardown').andCallThrough();
 
     $(document).trigger(Pixelated.events.tags.shortcuts.teardown);