Atlas › 21 Communication & Stakeholder Management › Technical Discussions☰ Read as one page
Technical Discussions
2.1The QA Voice in Architecture, Design, and CodeQA engineers who only speak up when bugs are found are leaving most of their value on the table. The earlier you participate in technical…2.2Participating in Architecture ReviewsArchitecture reviews are where the biggest quality decisions happen. A poorly chosen architecture can make entire categories of testing…2.3Asking the Right QuestionsThe most valuable QA contribution to any technical discussion is asking questions that nobody else thought to ask. Two question patterns…2.4Pushing Back on Untestable DesignsSometimes a proposed design makes testing impractical. Pushing back is necessary but must be done diplomatically.2.5Code Review from a QA PerspectiveCode review is one of the most effective shift-left activities QA can participate in. You bring a different perspective than the developer…2.6Building Credibility with DevelopersCredibility is not given; it is earned through consistent demonstration of technical competence and professional judgment.2.7Common QA-Developer Conflicts and How to Resolve ThemRoot cause: Ambiguous requirements. Neither the developer nor the QA engineer knows the intended behavior.2.8Hands-On Exercise1. Attend one architecture review or design discussion this sprint. Prepare three "What happens when..." questions in advance. 2. Review…