Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Table keywords should not log source if they fail
See original GitHub issueCurrently table related keywords logs the page source and user can define the level on which the logging happens. But the logging the source and defining logging level are not useful features. It would be better to remove the source logging and logging level definition. Instead it might be useful to allow user to define custom error message, if they want, if the table related keywords fails.
Example Table Cell Should Contain keyword signature should have arguments: locator, row, column, expected and message and here is an example:
| Table Cell Should Contain | xpath: //table | row=1 | column=2 | expected=foo | message=User defined error message |
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Generally I feel that logging the source is useless, although there might be some rare cases where it could be useful. I have to say that my run on failure keyword, maximize the browser, take screenshot and logs the source, but I usually never actually look at the source dump. Therefore I feel that we should remove the source logging from all keywords. Also unifying the
messageargument is a good idea.It would be good idea to ask also other users opinion on the matter after the 3.0 release.
Closing this issue because this is replaced by #1259