Making cross browser tests beautiful (v2 2017)
2 likes634 views
The document discusses implementing automated cross-browser tests for a student loan refinance application, highlighting essential steps such as deciding on supported browsers, automation workflows, and test execution methods. It addresses various issues, including element interaction inconsistencies across browsers, timing problems, and driver capability differences, particularly the limitations of the Safari driver. Key lessons learned include starting tests early, creating universal test scripts, and the importance of regularly running tests in continuous integration.
Making cross browser tests beautiful (v2 2017)
- 2. Ask me about: ● Continuous deployment ● Scaling automation ● Life @ startups
- 3. ● WHY ● HOW ● PROBLEMS ● SOLUTIONS ● LESSONS LEARNED A
- 4. WHAT DO YOU WANT TO GET OUT OF THIS SESSION?
- 5. WHY ?
- 6. ● Increase confidence your app works in all browsers ● Can easily test changes in browsers ● Save time from manually testing features
- 7. HOW ?
- 8. ● Answer the following questions: ○ Which browsers will be supported? ○ What is the most important workflow to test? ○ How will the tests be run?
- 9. Write automated tests for a student loan refinance application TASK:
- 12. Don’t know how application works in other browsers PROBLEM:
- 16. Step 1: Decide Supported Browsers
- 17. Step 1: Decide Supported Browsers
- 18. Step 2: Decide what to automate ● What is the most crucial workflow to automate?
- 19. Step 3: Decide how to run tests
- 20. Step 3: Decide how to run tests
- 21. Step 4: Write some tests
- 23. IT SHOULD BE AS EASY AS CHANGING THE DRIVER, RIGHT?
- 25. ● Cannot interact with elements in the same way across browsers ● Dropdowns, radio buttons and checkboxes are tricky
- 26. Element is not clickable
- 30. ● Need to wait for elements…. ● Running tests locally vs running remotely
- 31. No Such Element
- 32. IMPLICIT WAITS Wait for a set amount of time
- 33. EXPLICIT WAITS Wait for an event up until a certain amount of time
- 35. ● Drivers are managed separately ● Native capabilities differ ● Same functionality isn’t always available
- 36. FILE UPLOAD
- 37. 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.
- 38. RESOLUTION
- 39. ● Maximize browser window ● Set a specific resolution at run-time ● Scroll an element into view
- 41. LESSONS LEARNED
- 43. MAKE YOUR TEST SCRIPTS UNIVERSAL
- 45. Run tests in CI regularly
- 46. QUESTIONS? LinkedIn: meaghan-lewis Twitter: @iammeaghanlewis Email: meaghan@lever.co