Gary Hawkes | Comments

Thank you all for taking the time to read it and Ady for being such a diligent editor 🙏

This is a brilliant comprehensive article! I've saved this in one of my collections as its one I'm going to return to. All of your test strategies are perfect building blocks for those who are about to begin testing products with LLM capabilities. We at the beginning of this and this article will be the start. Thank you so much for writing this! 🙏

Great conversation, thank you! I like the realisation of where to take advantage of peoples skills across the team. I admit, the dedicated automators I've worked with were better coders than testers. I've only worked with 1 quality engineer who could move between automation and exploratory testing with equal proficiency. So getting developers more involved in the automation, coaching from quality engineers and making sure we're using the right skills for the right levels of testing.

Very enjoyable chat, thanks for this. We work in peaks and troughs, and in the troughs I do a lot of learning but not necessarily thinking of my vision of the team.

Thank you Callum. Very powerful and very important 🙏

Agree with Ash, love the organic format, its my favourite style of conversation - unscripted, unrehearsed and uninhibited. Simon is a master steering the conversation. A pleasure and honour to be a part of 🙏

Congratulations Diana, that is a massive achievement! 🙏

Thanks Rosie! 😁

For us nothing has changed, and nor should it in my opinion. Do any of the examples you used for DoR or DoD change just because of AI assisted development? If anything, maybe how we evidence some of those things may change.

How do the teams responsibilities in a bakery, align with a quality engineering team?

Thats a fantastic response Madhuri, thank you for taking the time to write that. I'm saving it and acting on it! Always learning 🙏