I like when it's blurring, but often it goes in the opposite direction if not moderated.
Worst case - here you have 15 tickets waiting to be tested by QA engineer who is off for holidays and only he/she's capable of running and interpreting 1hr long test suite. Half joke, half true.
This is a great article Mirek. While it probably surprises plenty of “modern” engineers this old approach to QA/testing/quality is still very much a thing (just had a discovery call with a prospective customer… siloed, downstream test specialists). You explain the core problems, root causes, and introduce alternative solutions nicely. 👍
Thanks Zac! Yeah, I agree - "classic approach" is still quite common, even in times of DevOps culture, DORA and others. And changing it was always a big challenge for me or for leaders who I worked with. That's why I wrote this piece - I want to support all of those who are having hard times and face self-doubts when doing such transformation.
I like to think of Quality as a shared goal/responsibility. The line between Dev and QA is definitely blurring over time.
I like when it's blurring, but often it goes in the opposite direction if not moderated.
Worst case - here you have 15 tickets waiting to be tested by QA engineer who is off for holidays and only he/she's capable of running and interpreting 1hr long test suite. Half joke, half true.
Adding more QAs to team is one of the most common way to deal with testing related issues.
I have recently published an article which addresses a similar concern. You would love to read it.
https://qaexpertise.substack.com/p/how-to-fix-the-most-common-testing-problem
I think it leads to Product Engineers, more T-shaped team players, and less focus on separate quality-oriented roles.
Great and comprehensive guide through the transformation that is happening. I like to remind: "quality is everyone’s work".
And it is a quality read — Thank you for the summary, Mirek.
Thanks Michał! Quality is everyone's work - cannot agree more! :)
This is a great article Mirek. While it probably surprises plenty of “modern” engineers this old approach to QA/testing/quality is still very much a thing (just had a discovery call with a prospective customer… siloed, downstream test specialists). You explain the core problems, root causes, and introduce alternative solutions nicely. 👍
Thanks Zac! Yeah, I agree - "classic approach" is still quite common, even in times of DevOps culture, DORA and others. And changing it was always a big challenge for me or for leaders who I worked with. That's why I wrote this piece - I want to support all of those who are having hard times and face self-doubts when doing such transformation.