You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the cucumber step timeout to some low threshold should have steps fail within expected timeframe, and immediately proceed to the next step in the scenario.
Actual behaviour
Setting the cucumber step timeout to some low threshold has the step (apparently) timeout in chimp/console, but codeblock from the timed-out step appear to continue via webdriverio/console output (console.log() showing up from old steps, browser.url() being sent to chromedriver....)
Steps to reproduce the problem
Manually set the cucumber step timeout to some artificially low threshold (set in /usr/local/lib/node_modules/chimp/node_modules/cucumber/lib/cucumber/support_code/step_definition.js, search for "timeout")
launch chimp with multiple steps.
observe that some of the steps appear to timeout as expected while others will display weird behaviors such as step 3 console.log() observed during the execution of step 8, or chromedriver jumping from step 10 browser.url() call to a (timed out) step 4, before going back to step 11...
following modified code should work to expose the issue:
Issue by PierreCBSI
Wednesday Aug 31, 2016 at 18:36 GMT
Originally opened as xolvio/chimp#458
Expected behaviour
Setting the cucumber step timeout to some low threshold should have steps fail within expected timeframe, and immediately proceed to the next step in the scenario.
Actual behaviour
Setting the cucumber step timeout to some low threshold has the step (apparently) timeout in chimp/console, but codeblock from the timed-out step appear to continue via webdriverio/console output (console.log() showing up from old steps, browser.url() being sent to chromedriver....)
Steps to reproduce the problem
Manually set the cucumber step timeout to some artificially low threshold (set in /usr/local/lib/node_modules/chimp/node_modules/cucumber/lib/cucumber/support_code/step_definition.js, search for "timeout")
launch chimp with multiple steps.
observe that some of the steps appear to timeout as expected while others will display weird behaviors such as step 3 console.log() observed during the execution of step 8, or chromedriver jumping from step 10 browser.url() call to a (timed out) step 4, before going back to step 11...
following modified code should work to expose the issue:
/features/my.feature:
/features/support/my.js:
Used version
Console / Log Output
Join our Slack xolv.io/community #chimp channel, where you can find help and help others.
The text was updated successfully, but these errors were encountered: