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
Whenever a test or perhaps even a keyword fails I would like to enter the debug CLI.
I have very long running tests that are very hard to triage and I think this would be an amazing tool.
Is there an easy way to wrap the DebugLibrary in a way I can use it as a RobotListener (to fire debug when a keyword or test fails)?
The text was updated successfully, but these errors were encountered:
MitchellMahan
changed the title
Debug when test fails (DebugLibrary as a Listener?)
Debug when test/keyword fails (DebugLibrary as a Listener?)
Oct 15, 2021
I'll look into this @MitchellMahan. It should be possible, but what it won't do is pause the test and continue - it would only fail the test and go to debug CLI with the failure still being the final outputted result. When Robot Listener version 3 is finished it would be able to manipulate the test run and possible stop a test dynamically on failure and start back up, changing the output. However, there is no way to do that with current version 3 and from the issues I read in Robot Framework repository it would be a huge internal code change to make it work - so it is backlogged for now.
Whenever a test or perhaps even a keyword fails I would like to enter the debug CLI.
I have very long running tests that are very hard to triage and I think this would be an amazing tool.
Is there an easy way to wrap the DebugLibrary in a way I can use it as a RobotListener (to fire debug when a keyword or test fails)?
The text was updated successfully, but these errors were encountered: