robotframework-debuglibrary
robotframework-debuglibrary copied to clipboard
xyb
A debug library for RobotFramework, which can be used as an interactive shell(REPL) also.
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...
Next keyword should execute whole keyword and jump to next keyword which is not happening  Same behavior observed in step 
Like when we debug some code in ipython, when I changed some code, the method/module could be auto reloaded, without have to import the module and redo pre-steps again.
While using step debugging, list or longlist always point on the main test where it was initialized. Not navigating to child keyword call. It would be helpful if it navigates....
When debugging robot tests that use `chromeheadless`, I've found that more often than not I actually want to view a screenshot of what the browser is doing at the point...
It seems that keywords imported from .robot files using the "Resource" keyword are not listed with keywords imported from libraries. Would it be possible to add this feature?
Is it possible to tell to robotframework to go to debug console in case any step fails?
Looks like py3.5 support in debuglibrary was removed, so prompt-toolkit 3.0.x should be allowed?
When I run debugging in pycharm, It report this error ``` import os from robot import run ROOT_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) run(f'{ROOT_DIR}/testcase/t.robot') ```
With robotframework-debuglibrary 2.40 and later, when the Debug keyword is called in a test case started in VSCode using the RobotCode extension instead of getting the interactive debug prompt you...
