-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Run Keyword
without logging as new Keyword
#3640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@Snooz82 - I would also appreciate such option! |
Could you clarify the need in a bit more detail? |
@pekkaklarck I am not sure if this is the case, but code like this:
Produces Log like this (where should be equal is child of custom kw) |
Yes exactly. I had this issue several times. |
I've got the same result when using from robot.libraries.BuiltIn import BuiltIn
class example:
def custom_kw(self, a, b):
BuiltIn().should_be_equal(a, b) This way it omits the log as you proposed. |
I don't think changing |
Run Keyword is a super handy and nice solution to execute keyword that are not part of the current library.
Example: Run a Keyword in failure like in SeleniumLibrary or Browser, or own WUKS implementation.
The only downside is, that it is not possible to NOT getting the called keyword as new Keyword-Layer in docs.
The feature requested is, that there could be way to disable Keyword beeing put to logs, when called by Run Keyword.
Logging (INFO and DEBUG, etc) should just be in the context of the calling keyword.
For me it would be good enough if there would be a python way to do it. I wouldn't need this option within Robot code.
Cheers
René
The text was updated successfully, but these errors were encountered: