Your Tests Aren’t Flaky, You Are! | Richard Bradshaw
Flaky this, flaky that, the only things I like flaky are my puff pastry and a Cadbury’s Flake. However, a week doesn’t go by without seeing some activity in the community on the subject of flaky automated checks. Most recently was this lengthy post, with masses of analysis by a team at Google on where they believe their flaky checks come from. Some useful insights in there, mostly around the size of the check and the tools used. I feel they missed the all important part, you, me! the person who actually created the automated check in the first place. All flaky automated checks come from us.
Automated checks have become an essential part of most teams' approach to testing and trying to build a quality product. They’re important for many many reasons, we’ll discuss though during the talk. But, it’s important to remember where these checks come from, they come from us. More specifically from the knowledge we have on the tools being used and most importantly our applications and their architectures. I view automated checks as algorithms. Algorithms that are designed and implemented by us. Two important parts there to avoid flakiness in the final automated check. The design and the implementation. I feel far too much effort and focus in on the implementation, and we all know what happens if you implement bad design, right?
In this talk I intend to break down the process of designing and implementing automated checks, going deep into the areas that I believe are critical to creating automation that returns real value to the team, checks that aren’t flaky, checks that don’t result in some poor person continuously playing the role of broken flaky automated check fixer! I’ve played that role, it sucks!
Takeaways:
- An appreciation of the skills required to design good automated checks
- An appreciation of the skills required to implement a good automated check
- How these skills differ, and how the whole team need to be involved
- The importance of continuously reviewing our automated checks for implementation, risks and value added
Видео Your Tests Aren’t Flaky, You Are! | Richard Bradshaw канала Selenium Conference
Automated checks have become an essential part of most teams' approach to testing and trying to build a quality product. They’re important for many many reasons, we’ll discuss though during the talk. But, it’s important to remember where these checks come from, they come from us. More specifically from the knowledge we have on the tools being used and most importantly our applications and their architectures. I view automated checks as algorithms. Algorithms that are designed and implemented by us. Two important parts there to avoid flakiness in the final automated check. The design and the implementation. I feel far too much effort and focus in on the implementation, and we all know what happens if you implement bad design, right?
In this talk I intend to break down the process of designing and implementing automated checks, going deep into the areas that I believe are critical to creating automation that returns real value to the team, checks that aren’t flaky, checks that don’t result in some poor person continuously playing the role of broken flaky automated check fixer! I’ve played that role, it sucks!
Takeaways:
- An appreciation of the skills required to design good automated checks
- An appreciation of the skills required to implement a good automated check
- How these skills differ, and how the whole team need to be involved
- The importance of continuously reviewing our automated checks for implementation, risks and value added
Видео Your Tests Aren’t Flaky, You Are! | Richard Bradshaw канала Selenium Conference
Показать
Комментарии отсутствуют
Информация о видео
Другие видео канала
![Redefining test automation | Richard Bradshaw | #SeConfLondon](https://i.ytimg.com/vi/uIDvGzQdoxc/default.jpg)
![](https://i.ytimg.com/vi/alGioEvnIDI/default.jpg)
![Selenium Test Automation: Practical Tips & Tricks - with Dave Haeffner (Part 1)](https://i.ytimg.com/vi/cIevkkD_LB4/default.jpg)
![Martin Fowler – Microservices](https://i.ytimg.com/vi/2yko4TbC8cI/default.jpg)
![Am I Lazy, Stupid, Messy, Flaky? ADHD](https://i.ytimg.com/vi/rUsotGVqUy4/default.jpg)
![Devs should love your tests | Carlos Kidman | #SeConfLondon](https://i.ytimg.com/vi/MAvXluvVv5o/default.jpg)
![Flaky tests are a pain (Andrei Solntsev, Estonia) [RU]](https://i.ytimg.com/vi/zOiSo1hYjF8/default.jpg)
![The Implementation of Rewind in Braid](https://i.ytimg.com/vi/8dinUbg2h70/default.jpg)
![Next level of Front end testing with Devtools and WebDriver | Fathima Harris & Srinivasan Sekar](https://i.ytimg.com/vi/wVD-r4MwLbA/default.jpg)
![QA with Continuous Delivery; Stop relying on browser based automated tests - Timothy Cochran](https://i.ytimg.com/vi/Lhgaqjavn-4/default.jpg)
![Regression Testing, the F.A.R.T Model](https://i.ytimg.com/vi/P2PUXqasvGI/default.jpg)
![Your Automated Execution Does Not Have to be Flaky - ukstar live Test Automation Webinar](https://i.ytimg.com/vi/KiUaJzdE64U/default.jpg)
![How To Pursue All Your Passions Without Looking Flaky](https://i.ytimg.com/vi/9WuEvCEy_Yc/default.jpg)
![GTAC 2015: Your Tests Aren't Flaky](https://i.ytimg.com/vi/hmk1h40shaE/default.jpg)
![QnA Friday 7 - How to test on multiple devices | Mobile and Tablets | Responsive Design Testing](https://i.ytimg.com/vi/5sw0SCU_Kp4/default.jpg)
![REST APIs and WebDriver: In Perfect Harmony | Mark Winteringham](https://i.ytimg.com/vi/ugAlCZBMOvM/default.jpg)
![Readable. Stable. Maintainable. E2E Testing @ Facebook | Archit Pal Singh Sachdeva](https://i.ytimg.com/vi/diYgXpktTqo/default.jpg)
![Docker Selenium. Getting Started](https://i.ytimg.com/vi/S4OkrnFb-YY/default.jpg)
![10 Warning Signs of Colon Cancer You Shouldn’t Ignore | Natural Health Forever](https://i.ytimg.com/vi/mqWTk7I3_xo/default.jpg)
![Jane Possell, SVP & CIO - CNA Insurance, speaks about Avo Automation](https://i.ytimg.com/vi/v2cI4vgRr6E/default.jpg)