Review process around documenting and tracking Known Issues

[emanlove]

We have quite a few internal tests for which are tagged as Known Issue under one or another browser. There have also been some recognition of various issues known and tracked within various external organizations (Selenium project or browser WebDriver teams). It would be good if we document any known tickets to our internal tests so that as external issues get resolved we known we can adjust our tests.

This ticket is to look at those processes and see if we can improve upon the current situation.

[lisacrispin]

Ignorant question, where would these be documented? In the RobotFramework doc somewhere?

[emanlove]

It is actually a really good question. I was thinking it would be documented within the code at the test case level. When I was running the test suite I would see some test either modified or ignored under certain browser due to some known issue. But as some were old I didn't know what was the issue nor whether it was resolved.

We could put this up higher or more public but thinking about that it would be really a lot of work for us to track both browser and selenium known issues. We have put in known issues with SeleniumLibrary into a releases' readme if it were at level that we felt needed to be known while trying to fix it for a subsequent release.