Making cross browser tests beautiful
0 likes750 views
The document outlines a session on creating effective automated cross-browser tests for a student loan refinance application. It discusses challenges encountered, such as browser compatibility and timing issues, alongside solutions like using cloud testing tools and various wait strategies. Key lessons include starting tests early, focusing on one feature at a time, and regularly integrating tests into continuous integration processes.
Making cross browser tests beautiful
- 2. Outline ● Why ● How ● Case Study ● Problems ● Solutions ● Lessons Learned
- 3. What do you expect to get out of this session?
- 4. Why ● Gives confidence the application works the same in all browsers ● Can easily test changes in browsers ● Saves time from manually testing all features
- 5. How ● Answer the following questions: ○ Which browsers will be supported? ○ What is the most important workflow test? ○ How will the tests be run?
- 6. TASK: Build automated tests for a student loan refinance application
- 8. PROBLEM: Don’t know how application works in other browsers
- 10. Step 1: Decide supported browsers
- 11. Step 2: Decide what will be automated ● Determine what is the most critical workflow to test
- 12. Step 3: Decide how to run tests ● Run tests in CI ● Need access to all supported browsers ● Consider cloud testing tools
- 13. Step 4: Write tests!
- 14. It should be as easy as changing the driver, right?
- 16. On page elements ● Dropdowns, radio buttons and checkboxes are tricky ● Use the same locator for all browsers ● Stick to CSS when possible
- 17. Element is not clickable
- 20. On timing issues... ● Some drivers are faster than others ● Discrepancies between physical and virtual machines ● Need to wait for elements
- 21. Implicit Waits ● Set for the entire duration of the webDriver object ● Tells WebDriver to wait for X units of time
- 22. Explicit Waits ● Confined to a particular web element ● Tells WebDriver to wait for the element up until X units of time
- 24. Drivers are not created equally ● Drivers are managed by different individuals ● Native capabilities differ ● Same functionality isn’t always available
- 25. File Upload
- 26. The Safari Driver is implemented in JS and does not have the privileges necessary to manipulate an <input type = “file”> element. Therefore, the SafariDriver does not support file uploads.
- 27. Resolution
- 28. ● Maximize browser window ● Set a specific resolution at run-time ● Scroll an element into view
- 29. Soon, the Cross-Browser Tests were complete!
- 32. Automate one feature first.
- 33. Run tests in CI regularly.
- 34. Questions? LinkedIn: meaghan-lewis Twitter: @iammeaghanlewis Email: meaghan@lever.co