interestingly, it only happens when running the test in series with the other tests in the suite. Perhaps a bad-driver-shutdown bug?
interestingly, it only happens when running the test in series with the other tests in the suite. Perhaps a bad-driver-shutdown bug?