robotframework / SeleniumLibrary

Web testing library for Robot Framework
Apache License 2.0
1.39k stars 765 forks source link

warnings for some acceptance test #602

Closed ghost closed 8 years ago

ghost commented 8 years ago

following 2 acceptance testcases produce warning instead of the expected error message: Select Non-Existing Item From Single Selection List Unselect Non-Existing Item From List

looks like both testcases need an update [ WARN ] Option(s) 'Tin Can Phone' not found within list 'preferred_channel'. [ WARN ] Option(s) 'Tin Can Phone' not found within list 'preferred_channel'. [ WARN ] Option(s) 'Smoke Signals' not found within list 'preferred_channel'. Select Non-Existing Item From Single Selection List :: Select Non-... | PASS |

[ WARN ] Tried to unselect missing selection item, 'Tin Can Phone' from locator 'possible_channels'. [ WARN ] Tried to unselect missing selection item, 'Smoke Signals' from locator 'possible_channels'. [ WARN ] Tried to unselect missing selection item, 'Tin Can Phone' from locator 'possible_channels'. [ WARN ] Tried to unselect missing selection item, 'Smoke Signals' from locator 'possible_channels'. Unselect Non-Existing Item From List :: LOG 3 Unselecting option(s... | PASS |

seems related to commit https://github.com/SeleniumHQ/selenium/commit/91ed4405abcf4d53e399baa3bb6d06ff5d2dd0e2 ( select_by_index, deselect_by_index ) seems related to pull request #597 ( Fixes Unselect From List due to Selenium changes. ) but now for keyword "Select From List"

divfor commented 8 years ago

this has been fixed by recently PR merged to master

ghost commented 8 years ago

I assume you refer to PR #597, this PR only fixes the failed testcases ( related to Unselect From List ). This issue refers to the (different) warning messages which are still present (for different testcases)

HelioGuilherme66 commented 8 years ago

I wrote the warning messages differently on purpose, because they exist in a different context. They are just warning messages. There are no statuscheck (postprocessing) for the messages. Do you think it should?

ghost commented 8 years ago

Both testcases specifically check for returned warning messages, possible solution is to rewrite the testcase such that they expect the new warning message text. in short the testcase expects warning message "A" but now gets warning message "B"

I already indicated testcases needs an update, not the code: " looks like both testcases need an update "

HelioGuilherme66 commented 8 years ago

The tests are not expecting the Warning messages.

I don't think the test cases need updating because there were no changes in the result of tests.

ghost commented 8 years ago

ok, then it sounds like there is no problem and this issue should be closed then.

HelioGuilherme66 commented 8 years ago

Great! (Thanks, for reporting and feedback!) @pekkaklarck @aaltat @emanlove @zephraph
I am so happy that an Issue has been Closed in this project! Aren't you also?