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