title: Locally-run tests pass, but Jenkins tests fail; why, and how can I fix this?
body: <p>I'm running a fairly large suite of python-based tests with a much larger number of steps on an Ubuntu Linux VM. When I run them via any number of methods manually (via the console) they all run and pass just fine.</p>
  
  <p>After I ported them to a Jenkins server, four out of the thirty fail. I tried the usually recommended fix - increasing the wait time for keywords to work to <code>1s</code> before every single click - so I'm fairly certain it isn't a timing issue. The site loads a lot faster than that on Windows, which I know is slower than Jenkins on Linux.</p>
  
  <p>After Googling around a little for an answer, I found that apparently no one has come up with an accepted answer, either on this site or other Q/A sites.</p>
  
  <p>Here's the error messages I'm getting from Jenkins.</p>
  
  <pre><code>ElementNotVisibleException: Message: element not visible
    (Session info: chrome=61.0.3163.79
    (Driver info: chromedriver=2.26.436382 (70eb799289ce4c2208441fc057053a5b07ceabac),platform=Linux 4.10.0-33-generic x86_64)
  
  WebDriverException: Message: unknown error: Cannot read property 'innerHTML' of undefined
    (Session info: chrome=61.0.3163.79
    (Driver info: chromedriver=2.26.436382 (70eb799289ce4c2208441fc057053a5b07ceabac),platform=Linux 4.10.0-33-generic x86_64)
  </code></pre>
  
  <p>The other two are both <code>element not visible</code> exceptions identical to the first, both of which happen on a <code>Click Button</code> keyword that is not the first Click Button keyword in the test suite. The first one happens on a <code>Click Element</code> keyword that has worked perfectly since I wrote it, and the last one happens on tried-and-true JavaScript call to get the text of an element.</p>
  
  <p>Why would something work locally on two different operating systems and then fail on Jenkins?</p>