Troubleshooting

Timeouts

Problem

When you run your features with Cuke4Nuke, you see an error like the following:

Timed out calling wire server with message 'begin_scenario' (Timeout::Error) 

This commonly occurs when using tools like Selenium or WATIN which take a long time to start up.

Solution

Edit your .wire file to override the default timeout for Cuke4Nuke commands. You specify a separate timeout for each message used in Cucumber’s wire protocol. Here’s an example:

host: localhost
port: 3901
timeout: 
  begin_scenario: 300
  invoke: :never

The timeout values are in seconds, but note that :never is also a valid value, meaning that Cucumber will hang forever until Cuke4Nuke responds.

For more details, see http://github.com/aslakhellesoy/cucumber/blob/master/features/wire_protocol_timeouts.feature