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.
Marcel is the co-founder and CTO of Xpirit, a high-end consulting firm based in Hilversum, Netherlands. Helping organizations transform towards a high speed, innovative, and productive organization is his passion.
Course Overview [Autogenerated] Hi, everyone. And welcome to my parole side course writing maintainable you white test automation with happy. Um, my name is Marshall de Vries, and I'm a chief technology officer at experience in the Netherlands. Writing test automation software is hard. It's hard because every time team members make changes to do you y 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 test will still provide value. In this course. I will show you how you can improve the way you write test automation in such a way that test break less frequent, and it makes it simpler to fix task the moment they get broken. We start this course at looking at What if actors are that make you? I test so fragile and easy to break. We will have a look at what high quality tests look like, and you look at what helps to improve the maintain ability off your test. I'll introduce you to a set of patterns and practices that can help you write high quality maintainable tests. The patterns that I use are the dry, single responsibility page, object, damp and screenplay pattern. We start a course with a set of example test scenarios I come and encounter in my consulting career, and I will show you how we can be affected them. Step by step. By applying these patterns, each model will cover a pattern and contains an extensive coding demo where I show you how to apply this on your own test scenarios. After watching this course, you should be able to re factor your own test scenario into a high quality good maintainable test, and you will learn how to apply the dry single responsibility page object, damp and screenplay pattern. I hope you join me on this learning journey with the course writing maintainable you. I test automation with happy, um