Bug #1781
UI tests aren't reliable
100%
Associated revisions
Making the ping test more reliable
Reference #1781
Making the whois tests more reliable
Reference #1781
Cleaning up code related to the implicit wait time
Reference #1781
Improving test reliability
Reference #1781
Updating the test suite
Reference #1781
History
#1
Updated by Luke Murphey about 7 years ago
Updated by The tests that fail often are:
- PingChrome (didn't find the result string)
- NSlookupChrome (waiting for command to show a running state)
- WakeOnLanChrome (save-host is not clickable, <div class="modal-body form form-horizontal modal-body-scrolling"> would receive the click)
- *Firefox (the tab link throws ElementNotVisibleException on Windows)
- WhoisChrome (test froze once)
#2
Updated by Luke Murphey about 7 years ago
The ping test appears to be more reliable now. However, Firefox once triggered the warning "Please enter the name of a host to perform the ping against". This was despite the fact that the address was in the box and it looked like the test started.
#4
Updated by Luke Murphey about 7 years ago
It seems like reducing the implicit wait to 5 seconds gets the whois test to pass. I now think it would have passed, it was just taking forever because of the 60x loop times 30 seconds (up to 30 minute runtime).
#5
Updated by Luke Murphey about 7 years ago
They seem pretty stable now.
#6
Updated by Luke Murphey about 7 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100