Project

General

Profile

Bug #1781

UI tests aren't reliable

Added by Luke Murphey over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
03/11/2017
Due date:
% Done:

100%

Associated revisions

Revision 119 (diff)
Added by luke.murphey over 7 years ago

Making the ping test more reliable

Reference #1781

Revision 120 (diff)
Added by luke.murphey over 7 years ago

Making the whois tests more reliable

Reference #1781

Revision 121 (diff)
Added by lukemurphey over 7 years ago

Cleaning up code related to the implicit wait time

Reference #1781

Revision 122 (diff)
Added by luke.murphey over 7 years ago

Improving test reliability

Reference #1781

Revision 123 (diff)
Added by luke.murphey over 7 years ago

Updating the test suite

Reference #1781

History

#1 Updated by Luke Murphey over 7 years ago

The tests that fail often are:

  1. PingChrome (didn't find the result string)
  2. NSlookupChrome (waiting for command to show a running state)
  3. WakeOnLanChrome (save-host is not clickable, <div class="modal-body form form-horizontal modal-body-scrolling"> would receive the click)
  4. *Firefox (the tab link throws ElementNotVisibleException on Windows)
  5. WhoisChrome (test froze once)

#2 Updated by Luke Murphey over 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 over 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 over 7 years ago

They seem pretty stable now.

#6 Updated by Luke Murphey over 7 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF