beforeTest, afterTest need longer timeouts

[pacovell]

Both beforeTest and afterTest may be doing more expensive setup/takedown that need a longer time to run. For example, to set up a selenium browser session (via soda), takes around 4 seconds on my computer.

I could put this in a "Background:" step and then use cucumis -t, but (a) sometimes it can take longer, and go past even the default 5s timeout of the async step (requiring a 'regular' custom command line or creating a script) and (b) I don't want a new session for each feature, as this unnecessarily slows down the testing.

The most crude solution is to simply increase the timeout on cucumis.js from 100ms to 10000ms in these cases. After all, if you actually have to kill a step for taking too long, this is a testing error and probably needs attention. I can imagine a more elegant solution where you can specify a timeout. Ideally this would be programmatic to avoid custom command lines.

I'm happy to write something along these lines and submit if this is the desired solution, or we can just increase the timeout. Thoughts?

[tomilaine]

I'm having the exact same issue.

[tomilaine]

This doesn't seem to raise much discussion. I made a pull request to use the timeout-variable configurable with cucumis -t, to be used also in regarding these events. That solves this issue at least for me. #22