Writing Maintainable UI Test Automation with Appium

Learn how to write better test automation, so your tests break less frequently and are simpler to fix when broken. You can do this by applying DRY, Single Responsibility Principle, Page Object Pattern, DAMP, and Screenplay Pattern.

Writing test automation software is hard. It is hard because every time team members make changes to the UI of the application, you are confronted with tests that are broken, and now you need to come to the rescue to fix them as soon as possible, so the tests still provide value. In this course, Writing Maintainable UI Test Automation with Appium, you will learn how you can improve the way you write test automation so your tests break less frequently, and to make it simpler to fix tests the moment they break. First, you will explore what the factors are that make UI tests so fragile and easy to break. You will have a look at what high-quality tests look like, and will take a look at what helps improve the maintainability of tests. Next, you will discover a set of patterns and practices that can help you write high-quality, maintainable tests. Finally, you will review a set of example test scenarios commonly encountered, and how you can refactor them step-by-step by applying the patterns, and you see how to use these patterns in your own test scenarios. After finishing this course, you should be able to refactor your own test scenarios into high quality, good maintainable tests, and you learn how to apply the DRY, Single Responsibility Pattern, Page Object, DAMP, and Screenplay Pattern.