I’m still working through trying to use etaoin with kaocha-cucumber for browser testing. I had the semi-bright idea of using regular kaocha pre-run and post-run hooks to start and stop the webdriver (which starts and stops a Chrome/FF instance) assoc it into the test plan and then… well, I need a reference to the live driver in the step definitions in order to fill in forms, etc.

oh, hold on. Maybe a Before hook would work to get it into the state param for all the steps

Nope, I clearly have the wrong end of the stick here.

Is there a normal way to have something sitting in state for my cucumber step definitions to use?

well, for the moment I’ve just stuck it in a defonce’d atom that gets reset! in a pre-test hook and it seems to work. I guess my more general question is, is there some way to access current global test plan state from Cucumber step definitions?

(and, in what ways is this a terrible idea?)