Do your scripts suffer from the following automation test flaky symptoms?

• Test randomly fail
• Works on your machine but not on another machine
• Test take a long time to run
• False positives/negatives results
• Unreliable test run in CI have you contemplating a new career as a sheep herder

If so, your test might suffer from a common under-diagnosed automation disease known as Stinky Synchronization Syndrome.

One of the biggest killers of test automation script reliability is the failure to use proper synchronization/wait points in Selenium. Read the rest of this post to learn how to treat this world wide epidemic.

 

http://www.joecolantonio.com/2014/04/01/the-1-killer-of-selenium-script-performance-and-reliability/

自动化测试中经常遇到失败的脚本，但是很多情况下，这些失败的脚本是没有意义的，可能是对象没有出现导致的。因为在web程序中对象的显示反应时间是不一致的。不同的网络环境，不同的操作会导致相应的时间的不同。如果避免？

尽量不用使用以下两种方式等待对象出现:

1. driver.manage().timeouts().implicitlyWait(GlobalDefinition.WEBELEMENT_LOADING_TIME, TimeUnit.SECONDS);

2.Thread.sleep();

推荐使用如下方式进行对象同步操作：

try{      WebDriverWait wait = new WebDriverWait(getDriver(),10);      wait.until(ExpectedConditions.visibility(joeLogo));      return true;     }catch(org.openqa.selenium.NoSuchElementException e){      return false;    }