robotframework / robotframework/SeleniumLibrary
alert issue in acceptance tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
I just withnessed following issue:
Running Acceptance . Keywords . Alerts . Alert Should Not Be Present with custom timeout left a alert open after a test failure and that caused a trickle down effect of quite a lot of tests failing due to following error:
UnexpectedAlertPresentException: Alert Text: None Message: unexpected alert open: {Alert text : Alert after 500ms!} (Session info: chrome=72.0.3626.121) (Driver info: chromedriver=2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.14.3 x86_64)
Maybe the alert tests should have test suite and teardown to open & close the browser to avoid this sort of flakyness ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the acceptance test for the Alerts keyword “Alert Should Not Be Present” using a custom timeout, then reproduce the failure that leaves an alert open. Review the related alert tests and their teardown behavior; done means a failed test no longer leaves an alert that causes subsequent tests to fail with UnexpectedAlertPresentException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100