robotcodedev
[ENHANCEMENT] Robot Output view
Is your enhancement request related to a problem? Please describe.
In robotframework-lsp there is an "Robot Output" view in VSCode to give you an overview which keyword is currently running and which keywords were already executed. See:
Describe the solution you'd like It would be nice to have such a view also in robotcode.
For me any my colleagues, this is one of the main reasons why we still use robotframework-lsp.
Have you tried robotcode.debug.groupOutput? If you enable it, you should see something like this in the debug console:
Maybe this meets your requirements?
If not, what exactly are your requirements and why do you need such a view?
I've tried several times to implement something like this, but I always came to the point where such a display caused real performance losses, no matter where, whether in the actual test run or in the VSCode UI. That's why I've always decided against implementing something like this completely.
But I would like to know why and for what you really need this display for? Perhaps there are other solutions/ways to solve these requirements?
This is the view I was looking for, but there are some issues:
- The view is often not updated. Sometimes only after the test execution something will be displayed or I need to collapse/expand the tests/suites for the view to be updated.
- The keywords with messages are expanded automatically (basically all is expanded automatically). This makes the view really confusing when there are many log messages and keywords.
- It is not possible to see if a keyword was really executed. When there is an IF/ELSE block, all keywords in the IF and ELSE block are displayed.
- Support for IF/ELSE, TRY/EXCEPT, FOR, WHILE, ...
- Keyword status should be displayed (PASS, FAIL, SKIP, maybe NOT_RUN)
Those are the main issues I have with this view. Some of them really make them unusable for me.
If not, what exactly are your requirements and why do you need such a view?
For example, you run a suite with many tests and in those tests there are multiple keywords, nested keywords and sometimes long running keywords. If I want to know where the execution currently is, it is often not possible to find this out with only log messages. This view would fix this, as you can immediately see which test and keyword is currently executed.
I hope you can now better understand why I really like and want such a view and I hope that this view will be improved in the future.