Comment #4 on issue 827 by pekka.klarck: Dynamic keywords ignored if getting documentation or arguments fails
http://code.google.com/p/robotframework/issues/detail?id=827
I'm starting to think this should be solved so that we issue a warning and the keyword is not created. I try to explain my point of view with the points below:
1) The current situation where the keyword is silently ignored when getting doc or args fails is clearly bad and must be changed.
2) Silently ignoring such failures and creating the keyword would be bad too. In this case you could easily miss that there was any failures and doc/args you try to set would be ignored. This is especially bad with args because they actually affect the test execution.
3) Showing a warning but still creating the keyword would be pretty OK. A problem is that if you miss the warning for some reason the keyword will not get the doc/args it should.
4) Showing a warning and not creating the keyword makes the error situation obvious and is, in my opinion, thus the best solution. If you test keywords at all, it's impossible that you create a keyword without doc/args because the keyword simply doesn't exist and cannot pass. The warning will be visible both on console and on the test log (under Test Execution Errors) and it would be visible on the console also when you create documentation with libdoc.py.
