Hmm Travis is failing. But i have no idea why and i can't see anything realted to background-image:

* I switch to i frame "Smart Search Indexer"
  [Selenium browser Logs] 
  19:23:17.889 WARNING - Error in parsing value for 'background-image'.  Declaration dropped.
  19:23:17.889 WARNING - Expected 'none', URL, or filter function but found 'progid'.  Error in parsing value for 'filter'.  Declaration dropped.
  19:23:17.890 WARNING - Expected declaration but found '*'.  Skipped to next declaration.
  19:23:17.890 WARNING - Expected 'none', URL, or filter function but found 'progid'.  Error in parsing value for 'filter'.  Declaration dropped.
  19:23:17.890 WARNING - Expected declaration but found '*'.  Skipped to next declaration.
  19:23:17.890 WARNING - Expected end of value but found '\9 '.  Error in parsing value for 'background-color'.  Declaration dropped.
  19:23:17.890 WARNING - Error in parsing value for 'background-image'.  Declaration dropped.
  19:23:17.890 WARNING - Error in parsing value for 'background-image'.  Declaration dropped.
  19:23:17.890 WARNING - Error in parsing value for 'background-image'.  Declaration dropped.
  19:23:17.890 WARNING - Expected 'none', URL, or filter function but found 'progid'.  Error in parsing value for 'filter'.  Declaration dropped.
  19:23:17.890 WARNING - Expected declaration but found '*'.  Skipped to next declaration.
  19:23:17.890 WARNING - Expected 'none', URL, or filter function but found 'progid'.  Error in parsing value for 'filter'.  Declaration dropped.
  19:23:17.891 WARNING - Expected declaration but found '*'.  Skipped to next declaration.
  19:23:17.891 WARNING - Expected end of value but found '\9 '.  Error in parsing value for 'background-color'.  Declaration dropped.
  19:23:17.891 WARNING - Unknown property '-moz-border-radius'.  Declaration dropped.

@chrisdavenport Thanks :) I just checked the logs on travis, issue is when Codeception is trying to look for Iframe 'Smart search Indexer' this happens in test administratorRunTheIndexer, what is the name or Id of the frame that we need to interact with?
Codeception can only identify by Name or Id of the iframe.

The name is "Smart Search Indexer". There is no id. The tests run perfectly on my laptop.

@chrisdavenport The problem is the 5 second wait before switching to the iframe. After 5 seconds the iFrame is already closed again (on Travis and on fast computers).

Just tested locally and have the same issue. You can try reducing wait time to for example to 1 second or try a different approach like waiting for the element.

$I->wait(5); // This is way too long
$I->switchToIframe('Smart Search Indexer');

@zero-24 That were just warnings / debug output you can ignore. The real error on codeception / selenium tests always shows up below all these messages in red.

Thanks @yvesh That makes sense.

Test for PHP 5.5 now passing. Test for PHP 5.6 appears to be a spurious failure. Actually, this is similar to what I'm seeing on my localhost. Roughly 2 out of every 3 test runs fail at random points for no apparent reason.

Imo it has something to do with the computer speed / available processing power. For me it fails roughly every 30 to 40 runs on a random point, but not more often.

On Travis it's also not that common. @chrisdavenport You can just restart the travis checks, then they probably should pass. (Except for PHP 7 but this is a different story)

We are still working hard on fixing this issue, using higher timeouts and better wait for elements.

@pritalpatel cc / can you please have a look at this PR and help Chris improving it :-)

I have run successfully all the tests.

@pritalpatel All your suggestions have been incorporated. Thanks for helping me improve this PR.

Welcome @chrisdavenport happy to help :)

@chrisdavenport Travis still fails with the switch to the iframe (probably to fast closed). Until we have a better solution i would suggest you don't actually switch to the iframe for now, but check the result of the indexing to make the tests more stable.

After the iframe there is an redirect taking place to the updated list. There your article should show up, which should sufficient to test :-)

As @pritalpatel suggested it is also a good idea, to add some more $I->checkForPhpNoticesOrWarnings(); on other places too.

@chrisdavenport Please send this PR into GSoC project repository. As this repository is aimed to have only weblink tests.
Thanks.

updated at #220. Closing