Hi Daniel, Many thanks for sharing this. Some of these are already our everyday discussion (good that you created a list anyway), but I love some insights like involving developers, investing time in CI/CD as well as not starting the automation too early. I saved the video for my future references 😃 Thanks again and please keep leading and providing ideas!
Hi Daniel very helpful and clear content, I think we should encourage QA people to learn more about the business or the project architecture before just starting to code, such because looks like "better skill for our profiles", for example, exploratory testing has a bunch of great techniques that give us excellent test cases to be really quality engineers and not just QA automation
Totally agree with you Paola. After I recorded the video I had more ideas what to add :). I also think it's important to understand coding patterns and coding principles. The book clean code is also a good starting point.
Hey Daniel! Pretty insightful videos. I appreciate the content and draw inspiration to pursue automation as a next step in my QA career. I want to ask for your opinion on something. I'm presented at work, with the opportunity of choosing an automation course and there are so many out there, especially IT academies. Now, what I see is that, most of them offer automation with Java and Java related frameworks. At my current work projects, our devs use mostly C# so I thought it would make sense to have a course of automation for C# and Selenium. Does it really matter if its Java or C#? To give you a bit more context, we're working on a retailer app. So there's the e-commerce part with product categories, product details, basket, checkout, etc and then the card payment integration with various payment providers (all of this means API testing and mobile testing).
Hi Alex, thanks for your comment! I would suggest you learn more about the system architecture you want to test before "blindly" jump into automation. Once you understand your system better, I would also recommend you to invest time to learn about coding patterns and how to write qualitative code. The book clean code is a good starting point to get the idea. However, if you want to learn more about automation, I usually recommend the test automation university (testautomationu.applitools.com/) powered by @applitools. There you can learn more about test automation using different tools.
@@DanielKnott But how can we develop them, even though I have several years on the software testing, I still feel that I do not know how to develop these parts of myself
If you can attend trainings, I recommend training such as clear communication, conflict management, lateral leadership as a starting point. But nothing beats training on the job. It takes time and I think that this learning path is never coming to an end. You always have to adapt to the new / current situation.
Hi Daniel,
Many thanks for sharing this. Some of these are already our everyday discussion (good that you created a list anyway), but I love some insights like involving developers, investing time in CI/CD as well as not starting the automation too early.
I saved the video for my future references 😃
Thanks again and please keep leading and providing ideas!
Thanks Serkan
Hi Daniel very helpful and clear content, I think we should encourage QA people to learn more about the business or the project architecture before just starting to code, such because looks like "better skill for our profiles", for example, exploratory testing has a bunch of great techniques that give us excellent test cases to be really quality engineers and not just QA automation
Totally agree with you Paola. After I recorded the video I had more ideas what to add :). I also think it's important to understand coding patterns and coding principles. The book clean code is also a good starting point.
Hey Daniel! Pretty insightful videos. I appreciate the content and draw inspiration to pursue automation as a next step in my QA career. I want to ask for your opinion on something. I'm presented at work, with the opportunity of choosing an automation course and there are so many out there, especially IT academies. Now, what I see is that, most of them offer automation with Java and Java related frameworks.
At my current work projects, our devs use mostly C# so I thought it would make sense to have a course of automation for C# and Selenium. Does it really matter if its Java or C#?
To give you a bit more context, we're working on a retailer app. So there's the e-commerce part with product categories, product details, basket, checkout, etc and then the card payment integration with various payment providers (all of this means API testing and mobile testing).
Hi Alex, thanks for your comment! I would suggest you learn more about the system architecture you want to test before "blindly" jump into automation. Once you understand your system better, I would also recommend you to invest time to learn about coding patterns and how to write qualitative code. The book clean code is a good starting point to get the idea. However, if you want to learn more about automation, I usually recommend the test automation university (testautomationu.applitools.com/) powered by @applitools. There you can learn more about test automation using different tools.
Hello, how we can develop the outside the box think, creativity, critical thinking and also problem solving thinking to be a good QA?
You are right! The skills you. mentioned should be used in every situation when working as software tester :)
@@DanielKnott But how can we develop them, even though I have several years on the software testing, I still feel that I do not know how to develop these parts of myself
If you can attend trainings, I recommend training such as clear communication, conflict management, lateral leadership as a starting point. But nothing beats training on the job. It takes time and I think that this learning path is never coming to an end. You always have to adapt to the new / current situation.