Sorry, one more thing I wanted to include here is the error in the test runner, each time I've encountered it it looks like this and it seems like it's happening during an 'after each' between the scenarios (one that the scenario didn't initiate). This is the way it looked on the first time I encountered it: