-
Notifications
You must be signed in to change notification settings - Fork 6
What language(s) and toolkit(s) did you use to write these tools?
All of the tools are written in python, and have been tested with python 2.7. The GUIs are all written in Tkinter.
Tkinter? Really? Why not use wxPython to be compatible with RIDE, or <insert your favorite toolkit here>?
I tried to use wxPython. Really, I did. I spent the better part of a year of weekends trying to get the tools to work the way I want on wxPython before finally admitting defeat. I honestly feel Tkinter is the better toolkit for this type of tool. Some things about wxPython I found to be maddeningly difficult, and the text editor components were a bit buggy, especially with unicode data.
Do these tools have a config file? If so, where is it?
On Windows it is in $APPDATA/rwb.cfg (or ~/rwb.cfg if APPDATA is undefined). On all other platforms (OSX, linux, etc) it is in ~/.rwb.cfg.
How do I turn on logging of debug statements, so I can help diagnose a problem?
The logging system looks for an environment variable named RWB_LOG_LEVEL. You can set this variable to "DEBUG" to get more logging information. (eg: $ RWB_LOG_LEVEL=DEBUG python rwb.editor)
I want real debugging features, like being able to single step through a test. When will they become available?
Unfortunately, robotframework has no support for debugging. There's just no way to single-step through a test, and no easy way to retrofit that to the existing runner. I've been told that 2.8 will have a new test runner, and I'm hoping the presence of rwb.debugger will convince the core team to add some better introspection and control facilities into the runner.
For the editor and the little edit window in the debugger, do you support other formats besides the pipe-delimited plain-text format?
No. I personally think the plain text, pipe-delimited format is superior to the other formats. It is very human friendly, and very tool friendly (ie: it's easy to diff).
This project original started because I got frustrated with RIDE because it insisted on reformatting my .txt files. I wanted a plain text editor with special features to make it easier to write tests. I could conceivable add a feature where it autoconverts to some of the other formats, but that defeats the purpose.
Can I specify my own arguments when running tests from the editor?
No, but it's very near the top of my short-list of things to fix.
What's up with rwb.lint? It almost seems like it's completely busted.
You are right, it's at the very bottom of my priority list right now; I've been focused mostly on the debugger lately. Right now it's mostly just a playground for some ideas I have. You probably won't find it useful right now.
Can I specify my own arguments when running tests from the gui test runner?
No, but it's very near the top of my short-list of things to fix.