Kill A Workflow


1 comment

  • Avatar

    Hi, if any of the steps throw exception or if any assertion fails Twist would stop executing the next steps? Are you saying that it goes ahead with the next step execution?
    Twist on encounter of an exception or assertion failure will not proceed further with subsequent step execution, but will attempt to run the contexts in the reverse order of declaration. Is your workflow getting stuck somewhere there?

    If you run the scenario from Twist IDE, do you see the step marked as error? Have you tried putting a debug point in your code and tracing through?

    Are you looking for an element which is not visible/present? For example, using Webdriver you can call findElements() mehtod, and webdriver will try a few times before timeout happens. You can control the timeout as well. 

    Thanks and regards

    Comment actions Permalink

Please sign in to leave a comment.