Emily O'Connor | Comments

🙃

Nice picture of Mr Steve Mellor :)

Highlighting the security problems sounds like a good feature, but it might be too little too late as folks just want to publish! I wonder if it was a reaction to this news piece: https://www.ministryoftesting.com/satellites/lovable-vibe-coding-security-crisis-exposed

Is this list trying to be the numerical counter part to The Big List of Naughty Strings? https://www.ministryoftesting.com/satellites/big-list-of-naughty-strings?s_id=19042891

Intro to "problem statement" 2:30 Melissa on the one page test plan 6:50 Natallia on prioritisation, scope and constraints 9:40 Zooming out from the implementation 17:20 Personas and getting the customers perspective 20:30 Standardisation and templates 24:20

Chapters Presentation starts at 6:00 Demo of the test case generator 16:45 Part 2: Automation & Self Healing 22:55 Demo of automation 29:30 Part 3: Execution & Reporting 36:00 Demo 38:30 Part 4: Bug Triage 40:30 Questions 47:00

@Jonathan, this is what I meant by the fact that the name Copilot is catch-all; At the latest count, Ty Bannerman notes that there are 80 different, separately marketed Copilot products and tools. From https://www.ministryoftesting.com/satellites/expert-maps-out-more-than-80-different-microsoft-copilot-products-but-there-may-be-more-than-100-what-happens-when-you-name-everything-copilot-an-ai-consultant-mapped-out-the-myriad-products

I'm In This Photo and I Don't Like It

Do you have any book recommendations? I love the book The Captain Class https://www.penguin.co.uk/books/421695/the-captain-class-by-sam-walker/9781785030291

How would you persuade engineers and product owners to prioritise bugs and features that go beyond acceptance criteria? As you say, a product could be completely built to spec but still add no value for end users - how should testers and quality professionals raise this to ensure their voices are really heard?

I read this article from my emails (sent October 2024) and think it would be such an interesting topic to revisit. Given the increase in coding agents and AI tools for the creation of test automation; do you still believe a Computer Science degree doesn’t give you a leg up as a technical tester? I think its invaluable; to be able to provide more detailed prompts on the expected best practices of code, to have a better understanding of how the system under test is built up and where bugs may lie.