How early would you say automation should be integrated in a project i have seen alot of differing opinions on this particular topic but would love to hear your opinion
As soon as things are stable enough so that you can get started and not count on things constantly changing. But I think you should think about how things are going to be automated from the started, and then incorporate that into your development straight away.
Unpopular Opinion Maybe: Shift left Automation from a tester perspective seems not advisable and a common mistake since the requirements changes so frequently and I have seen tests not being updated or maintained and we are often not updated on the requirement changes. We just end up having scripts for the sake of having scripts. Also would be interested in hearing you ideas on Test Management and Tracking. My weakness😛
To me, shifting testing left means questioning the requirements, giving feedback on it. I try to help give everyone clarity. Having scripts for the sake of having scripts is a waste of people's time (I would ask people what value are they trying to add with the scripts). Early in my career I was on projects where we had detailed test cases, but then any small changes to the system (expected, desired changes) resulted lots of test cases needing to be updated.
@@NicolaLindgren Agree. Would like to understand your thoughts on how you go about shifting left when the QA is a horizontal, supporting multiple projects
How early would you say automation should be integrated in a project i have seen alot of differing opinions on this particular topic but would love to hear your opinion
As soon as things are stable enough so that you can get started and not count on things constantly changing.
But I think you should think about how things are going to be automated from the started, and then incorporate that into your development straight away.
Unpopular Opinion Maybe: Shift left Automation from a tester perspective seems not advisable and a common mistake since the requirements changes so frequently and I have seen tests not being updated or maintained and we are often not updated on the requirement changes. We just end up having scripts for the sake of having scripts.
Also would be interested in hearing you ideas on Test Management and Tracking. My weakness😛
To me, shifting testing left means questioning the requirements, giving feedback on it. I try to help give everyone clarity.
Having scripts for the sake of having scripts is a waste of people's time (I would ask people what value are they trying to add with the scripts).
Early in my career I was on projects where we had detailed test cases, but then any small changes to the system (expected, desired changes) resulted lots of test cases needing to be updated.
@@NicolaLindgren Agree. Would like to understand your thoughts on how you go about shifting left when the QA is a horizontal, supporting multiple projects
@@JayanthSrivatsav Do you mean a single tester is supporting multiple projects?
Or you have a test team that support multiple projects`
@@NicolaLindgren As a team of QA engineers
Can someone from the team be invited to some of the early discussions?
If not, I would ask why this isn’t possible
Your channel is so nice, if you want, I will give some important tips to grow your TH-cam channel.
Thanks for your kind words. Feel free to write the tips here or share a blog post I should read.
I am still finding something that I disagree with you about!!
Nothing wrong with disagreements
It’s interesting hearing other perspectives.