- did you encounter the discussion of independent verification (aka devs should test their own) - what did you reply?
I’m not sure if I’m understanding this question right but if the question is, did it come up whether or not devs should test their own code or we should have QA, our take on it ended up being that both are true. Devs should share quality by writing automated tests for their own feature code which helps them plan testability in better and shift left by finding bugs faster and lowering the cost and blast radius of bugs found since the sooner you find them the easier they are to fix and the less likely they reach a user and do damage. However manual QA is still needed because they are pros at user experience and are better able to objectively represent the user while using their professional tester chops to kick the tires and find the holes. An automation Guild in our case is important for keeping a tester mindset focus, advocating that testing stays a priority and gets into the workflow each week, expanding and optimizing the framework, and diversifying testing, visualizations of results, stability of test runs etc… areas where dev are less likely to naturally give attention as they are highly focused on their features. Feature quality does not contradict with feature development but general testing frameworks and other testing activities outside of their immediate features often do not align as well with their regular workflow. Therefore it’s important to keep tester involvement and their unique perspective and contributions too.