@rgm the pattern I've used for this is to have an idempotent setup method which I call at the start of every step, see https://github.com/lambdaisland/kaocha/blob/master/test/shared/kaocha/integration_helpers.clj#L70-L102

For you this could look something like this

(defn wedriver-setup [m]
  (if (:driver m)
    m
    (assoc m :driver (do-actual-setup))))

(When "foo" [m]
  (let [m (webdriver-setup m)]
    ...
    m))


(Then "bar" [m]
  (let [m (webdriver-setup m)]
    ...
    m))

@plexus ah, ok. That works well for setup in step definitions, just passing it along the chain in state. I’m still fuzzy about teardown at the end of the suite … lambdaisland.cucumber.dsl/After can’t have access to that state, can it?

I would guess not since there may be a bunch of tests / drivers cruising around in parallel, which is how I ended up on pre-test/post-test hooks