Key Takeaways:

The biggest issue when it comes to Selenium tests is attempting to interact with the page elements when they are not ready. Trying to click an element before it is available, trying to select a value from a drop down when it is not yet populated, checking an element attribute before it is available - these are some of the most common reasons for failures when it comes to Selenium tests.

Such issues can be avoided by using the WebDriverWait Java class to redesign the way you interact with your page. In this talk i will show you how to get from click to click and wait, from select a drop down value to wait and select, and so on.

I will show you how to replace your standard Selenium commands, like click, with customized waits that you can write to adapt to your test environment conditions. I will show you how to rethink your page interactions from a waiting perspective. And, as an added bonus, how you can replace some of the assertions you write with corresponding wait methods.

Key Takeaways :

How a team adopt automation test and how the automation test evolution in an agile team.

1. When and why Agile team feels need automation test
2. Start to do Automation test
3. First evolution – introduce QA specialist to do automation test
4. Second evolution – introduce test framework to catch up development progress
5. Third evolution – extend test framework to increase coverage
6. Our current automation approach

Ma Nan is a senior software engineer in Test in Autodesk on Autodesk big data platform(ADP). She has 10+ years of automation testing experience. In different periods, she had to built and maintained different kinds of automation frameworks such as UFT, Selenium, and AWS. She had led her team to deliver more than 15 automation projects.