Ok - found it myself :)

 Then "Continue on Failure" option was what I was looking for

Hello Andreas,

Glad to hear you have found the option you were looking for.

I am closing this case.

Regards,
Ivaylo
Telerik

Unfortunately its not doing what I assume it should do ;-)

 I have a test with a login step, then some actions and finally a logout step. I marked the last logout step as "Continue on Failure". Then I changed an assertion in the middle to provoke a failure.

 When running this, the assertion fails and the execution stops, without the last step being executed.

 This means rerunning the tests fails, as it defines the loginstep as first action, but the page has never been logged out and therefore it fails finding the login form.

Do I need to do more to ensure that the last step is invoked, regardless what happened in previous steps ?

Ok I found out in the documentation that the button has a different meaning than I expected to have. The button is to add at a step and saying "continue if this step fails" - what I like to have is a kind a teardown mechanism for my test, meaning "what ever happened in the test, execute this step".

 I searched the forum and only found solutions via coding, but as people working with this tool will not be coders per se, is there any other way of defining this behaviour via the UI ?

Hello Аndreas,

Unfortunately you cannot define this using the UI, this would be only possible using a coded approach.

I have logged a feature request which you can track and follow using this URL.

Тhank you for your understanding.

Regards,
Ivaylo
Telerik