Currently one instance of ash is brought up for all tests. This is problematic as ash is written assuming there is a single instance of chrome it can connect to and connects to it. Additionally the chrome startup code assumes it is starting up with a pristine ash environment. That isn't the case if chrome is already running.