<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team Management on Testing Observation</title><link>https://chengxiaqiucao.github.io/en/tags/team-management/</link><description>Recent content in Team Management on Testing Observation</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>|by Daniel Wei</copyright><lastBuildDate>Wed, 09 Jul 2025 15:32:15 +0800</lastBuildDate><atom:link href="https://chengxiaqiucao.github.io/en/tags/team-management/index.xml" rel="self" type="application/rss+xml"/><item><title>How Should a Software Testing Team Be Well Managed?</title><link>https://chengxiaqiucao.github.io/en/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/</link><pubDate>Wed, 09 Jul 2025 15:32:15 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/team.webp" alt="Featured image of post How Should a Software Testing Team Be Well Managed?" />&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/team_hu_9599330a6aea1f05.webp"
width="1024"
height="617"
srcset="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/team_hu_a32b0fcec9834db.webp 480w, https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/team_hu_9599330a6aea1f05.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="165"
data-flex-basis="398px"
>
&lt;/p>
&lt;p>Although with the spread of Agile and the practice of shift-left testing, many testers have become more integrated into the same teams as developers, most software enterprises still typically set up a dedicated testing department or software quality department independently.&lt;/p>
&lt;p>So what aspects do we usually start from when managing such an independent software testing team? Of course, team management has a great deal in common across all types of teams, but the testing function also reflects some characteristics of its own. This article discusses the following aspects.&lt;/p>
&lt;h2 id="establishing-standards">Establishing Standards
&lt;/h2>&lt;p>For any team to become effective, the necessary rules, regulations, and processes are indispensable.&lt;/p>
&lt;p>These include some management standards and systems, such as:&lt;/p>
&lt;ul>
&lt;li>Reward and penalty standards&lt;/li>
&lt;li>Attendance standards&lt;/li>
&lt;li>Training standards&lt;/li>
&lt;li>Work reporting systems, and so on&amp;hellip;&lt;/li>
&lt;/ul>
&lt;p>They also include establishing some technical standards and template requirements related to the testing function itself, such as:&lt;/p>
&lt;ul>
&lt;li>Test plan&lt;/li>
&lt;li>Test strategy&lt;/li>
&lt;li>Test cases&lt;/li>
&lt;li>Test execution&lt;/li>
&lt;li>Test report&lt;/li>
&lt;li>Defect management&lt;/li>
&lt;li>Environment management&lt;/li>
&lt;li>External testing&lt;/li>
&lt;li>Asset management&lt;/li>
&lt;li>Quality analysis, and so on&amp;hellip;&lt;/li>
&lt;/ul>
&lt;p>Of course, they also include sorting out testing-related processes, such as:&lt;/p>
&lt;ul>
&lt;li>Defect handling process&lt;/li>
&lt;li>Test entry and exit criteria (build submission and release processes)&lt;/li>
&lt;li>Quality analysis process, and so on&amp;hellip;&lt;/li>
&lt;/ul>
&lt;p>Sorting out and establishing standards and processes is the foundation of a department&amp;rsquo;s work. But standards are not formed and perfected overnight; they are a team consensus that gradually accumulates through daily management and team collaboration, and a tangible guide to behavior.&lt;/p>
&lt;h2 id="building-capability">Building Capability
&lt;/h2>&lt;p>Whether a team is successful, and how effective it is, depends on the team&amp;rsquo;s capability.&lt;/p>
&lt;p>So for a testing team, how do we build this capability?&lt;/p>
&lt;p>The testing industry, drawing on the &lt;strong>CMMI&lt;/strong> model, has proposed the &lt;strong>TMMI&lt;/strong> model:
&lt;img src="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/TMMI_hu_1266f00bd06a835.webp"
width="1024"
height="666"
srcset="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/TMMI_hu_6532c026828f7a54.webp 480w, https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/TMMI_hu_1266f00bd06a835.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="153"
data-flex-basis="368px"
>
&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>Initial&lt;/strong>
The default starting level. The organization has no relevant testing capability yet; testing work is coarse and casual, with no separate testing phase.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Managed&lt;/strong>
Testing work becomes a specialized function, with basic testing standards such as policies, strategies, plans, schemes, design, execution, and so on. There is also a testing environment — a separate testing environment is used to carry out the testing work rather than performing the relevant verification in the development environment.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Defined&lt;/strong>
Generally it is only at this level that an organization reaches basic maturity in its testing work. Its typical feature is having a dedicated testing organization, with a testing team responsible for organizing and implementing the testing work. In addition to basic functional testing, at this level relevant capabilities are established for various non-functional tests, including performance testing, compatibility testing, usability testing, reliability testing, accessibility testing, and other rich testing types. There is also a strong emphasis on quality-oriented peer review.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Measured&lt;/strong>
The effectiveness of testing work can be quantified from multiple dimensions through relevant metrics and data, reflecting fairly accurately how well the testing work is being done.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Optimized&lt;/strong>
It enables continuous self-renewal and ongoing optimization. Through full-process quality control and up-front analysis techniques, defect prevention is achieved.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>Beyond such industry standards, in summary, the capability building of a testing team can also focus on the following four aspects:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Business testing capability&lt;/strong> — the foundation on which the team stands, the ability to find problems&lt;/li>
&lt;li>&lt;strong>Fast testing capability&lt;/strong> — improving efficiency, building a cost advantage, and establishing confidence in quality in a timely manner&lt;/li>
&lt;li>&lt;strong>Quality assessment capability&lt;/strong> — accurate measurement and monitoring of quality&lt;/li>
&lt;li>&lt;strong>Rapid response capability&lt;/strong> — quick reaction to quality problems and risks&lt;/li>
&lt;/ul>
&lt;p>Doing a good job of building team capability is the foundation of establishing a team&amp;rsquo;s moat.&lt;/p>
&lt;h2 id="performance-measurement">Performance Measurement
&lt;/h2>&lt;p>In the workplace, people work hard ultimately for their own better development and to gain immediate or long-term benefits. Seeking advantage and avoiding harm is only human.&lt;/p>
&lt;p>In team management, the measurement of performance is essentially about using performance as an anchor to manage the distribution of benefits well and drive the achievement of the team&amp;rsquo;s overall goals.&lt;/p>
&lt;p>Nowadays there are two main performance management frameworks commonly used in enterprises:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>KPI&lt;/strong> — Key Performance Indicator&lt;/li>
&lt;li>&lt;strong>OKR&lt;/strong> — Objectives and Key Results&lt;/li>
&lt;/ul>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/Pasted-20250710_hu_4ec10d8d3936079a.webp"
width="1024"
height="608"
srcset="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/Pasted-20250710_hu_eb3ad120f33f9a6c.webp 480w, https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/Pasted-20250710_hu_4ec10d8d3936079a.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="168"
data-flex-basis="404px"
>
&lt;/p>
&lt;p>&lt;strong>KPI&lt;/strong> is result-oriented, focusing on some key quantitative indicators that can be measured.
&lt;strong>OKR&lt;/strong> is goal-driven and revolves around objectives; although its key results are usually quantitative as well, the emphasis is more on the path to achieving the goals.&lt;/p>
&lt;p>Whether it is KPI or OKR, a team&amp;rsquo;s performance management cannot do without the formulation of various quantitative performance indicators.&lt;/p>
&lt;p>For a testing team, the relevant indicators can be viewed from three different dimensions:&lt;/p>
&lt;h3 id="quality-dimension">Quality Dimension
&lt;/h3>&lt;p>A testing team is oriented toward quality, so measuring performance cannot do without quality assessment. Some commonly used key indicators include:&lt;/p>
&lt;ul>
&lt;li>Requirement coverage&lt;/li>
&lt;li>Defect leakage rate&lt;/li>
&lt;li>Build rejection rate&lt;/li>
&lt;li>Release success rate, and so on&amp;hellip;&lt;/li>
&lt;/ul>
&lt;h3 id="efficiency-dimension">Efficiency Dimension
&lt;/h3>&lt;p>As a cost center, the efficiency with which the testing department completes quality assessment directly affects the release cadence and is an important component of product cost. Therefore, the management of the testing department necessarily includes indicators related to work efficiency, such as:&lt;/p>
&lt;ul>
&lt;li>Test cycle&lt;/li>
&lt;li>Automation coverage&lt;/li>
&lt;li>CI success rate&lt;/li>
&lt;li>Release efficiency&lt;/li>
&lt;li>Response efficiency, and so on&amp;hellip;&lt;/li>
&lt;/ul>
&lt;h3 id="growth-dimension">Growth Dimension
&lt;/h3>&lt;p>Beyond the dimensions above that reflect the department&amp;rsquo;s own goals, no team can do without the gradual growth and maturation of its members. Therefore, indicators oriented toward individual and team growth are also an important dimension of team management, such as:&lt;/p>
&lt;ul>
&lt;li>Knowledge sharing, training&lt;/li>
&lt;li>Technical innovation, process improvement, tool development&lt;/li>
&lt;li>Learning summaries, event organization, and so on&amp;hellip;&lt;/li>
&lt;/ul>
&lt;p>From the different dimensions above, in team management we can break things down into a variety of more detailed sub-indicators based on the team&amp;rsquo;s current situation, and combine this with techniques for collecting and analyzing performance data to achieve scientific measurement. This can then be directly linked to tangible interests such as salary raises, bonuses, and job levels.&lt;/p>
&lt;h2 id="team-collaboration">Team Collaboration
&lt;/h2>&lt;p>As a collective focused primarily on the testing function, and at the same time a team that must cooperate fully with other functions in software product development such as development and operations, another important part of testing team management is management oriented toward team collaboration.&lt;/p>
&lt;p>Collaboration cannot do without communication. Here we can make full use of the Johari Window communication model introduced in my earlier article 【】, or the conflict model in 【】, as auxiliary tools for communication and collaboration.&lt;/p>
&lt;p>From the perspective of the testing team, we can in fact consider team collaboration from four dimensions:&lt;/p>
&lt;h3 id="internal-collaboration">Internal Collaboration
&lt;/h3>&lt;p>Here the main thing is to arrange work reasonably according to the different members&amp;rsquo; abilities and personality traits, so that everyone is used to their best advantage and all parties benefit mutually.&lt;/p>
&lt;h3 id="peer-department-collaboration">Peer-Department Collaboration
&lt;/h3>&lt;p>Collaboration between peer departments includes cooperation with the development team, operations team, product team, and others. The emphasis is on handling cooperation with peer teams in a spirit of win-win mutual benefit — seeking common ground while reserving differences as far as possible, perfecting processes, arranging interfaces well, and safeguarding the team&amp;rsquo;s interests when disputes and conflicts arise.&lt;/p>
&lt;h3 id="upward-collaboration">Upward Collaboration
&lt;/h3>&lt;p>Communication and collaboration with senior leadership or higher-level departments is a lesson that any middle manager must master. Likewise, leaders with different personality traits require different communication skills and approaches. Managing upward well wins space for the healthy development of the team.&lt;/p>
&lt;p>In short, in an enterprise, an excellent middle manager should be a Leader who can &amp;ldquo;&lt;strong>bear pressure from above, command respect from below, and collaborate (si)(bi) with peers&lt;/strong>&amp;rdquo;.&lt;/p>
&lt;h3 id="external-collaboration">External Collaboration
&lt;/h3>&lt;p>In addition to these internal collaborations, the testing team is actually a department that fairly often faces external relationships, in scenarios such as outsourcing, after-sales support, and external testing.&lt;/p>
&lt;p>In such collaborations, team management must clarify authority and the scope of responsibility. As a representative of the enterprise, it should also safeguard the enterprise&amp;rsquo;s image and interests, maintain good relations with external organizations, and build trust.&lt;/p>
&lt;h2 id="team-culture">Team Culture
&lt;/h2>&lt;p>Finally, for any team to remain stable and develop soundly over the long term, it cannot do without the support of team culture.&lt;/p>
&lt;p>&lt;strong>Processes, standards, and systems are tangible; their emphasis is on telling everyone how to do things correctly, and behavior is passive.&lt;/strong>&lt;/p>
&lt;p>&lt;strong>But once team culture has formed, everyone consciously acts according to shared values, and behavior is proactive.&lt;/strong>&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/%E5%9B%A2%E9%98%9F_hu_1c2a1ea5a5dd6db6.webp"
width="1024"
height="593"
srcset="https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/%E5%9B%A2%E9%98%9F_hu_2ab4c32ab052af42.webp 480w, https://chengxiaqiucao.github.io/post/109-%E6%B5%8B%E8%AF%95%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86/%E5%9B%A2%E9%98%9F_hu_1c2a1ea5a5dd6db6.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="172"
data-flex-basis="414px"
>
&lt;/p>
&lt;p>Culture takes a long time to form, and the team manager is the key to its formation. Carry it through consistently — &amp;ldquo;what you keep constantly in mind will surely find an echo&amp;rdquo;.&lt;/p>
&lt;hr>
&lt;p>Above is my overall explanation of the five key dimensions of testing team management. Friends interested in the details can also follow the management section of my systematic testing-skills improvement course, which contains a detailed analysis of these five dimensions and their implementation. Reply &lt;code>outline&lt;/code> to view the detailed course catalog.&lt;/p></description></item><item><title>AI Testing, the Inevitable Path for Testing Teams</title><link>https://chengxiaqiucao.github.io/en/post/083-ai%E6%B5%8B%E8%AF%95%E8%B7%AF%E7%BA%BF%E5%9B%BE/</link><pubDate>Sat, 26 Apr 2025 00:00:00 +0000</pubDate><guid>https://chengxiaqiucao.github.io/en/post/083-ai%E6%B5%8B%E8%AF%95%E8%B7%AF%E7%BA%BF%E5%9B%BE/</guid><description>&lt;blockquote>
&lt;p>This article is translated and adapted from the latest post on the well-known testing blog &lt;a class="link" href="https://testguild.com/" target="_blank" rel="noopener"
>https://testguild.com/&lt;/a> and discusses a roadmap for systematically implementing and advancing AI testing within testing teams. It offers considerable reference value, so I am sharing it with you all.&lt;/p>&lt;/blockquote>
&lt;h2 id="ai-test-automation-is-no-longer-optional">AI Test Automation Is No Longer Optional
&lt;/h2>&lt;p>In today&amp;rsquo;s software testing field, artificial intelligence (AI) is no longer merely an option but a significant strategic advantage. AI-driven testing tools can automate everything from test case generation to test execution, enabling your team to focus on delivering higher-quality software releases.&lt;/p>
&lt;p>Tal Barmeir, CEO of Blinq.io, once noted: &amp;ldquo;The role of generative AI is to help us truly solve the problem of a massive backlog of testing demand with very limited coverage—a phenomenon we see across every industry.&amp;rdquo;&lt;/p>
&lt;p>AI-driven testing tools can automate the entire process from test case creation to execution and maintenance, helping testing teams:&lt;/p>
&lt;ul>
&lt;li>Reduce test creation time by up to 80%&lt;/li>
&lt;li>Lower test maintenance costs by 40-60%&lt;/li>
&lt;li>Accelerate time to market through faster release cycles&lt;/li>
&lt;li>Improve test coverage across browsers, devices, and environments&lt;/li>
&lt;li>Free up valuable engineering resources for innovation&lt;/li>
&lt;/ul>
&lt;p>This guide offers a structured approach to implementing AI testing, designed to deliver both immediate benefits and long-term transformation.&lt;/p>
&lt;h2 id="phase-1-days-1-15---define-your-ai-testing-strategy">Phase 1 (Days 1-15) - Define Your AI Testing Strategy
&lt;/h2>&lt;p>Before diving into specific tools, you first need to clarify how you want to apply AI:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Assistive AI&lt;/strong>: Enhances human-led testing processes.&lt;/li>
&lt;li>&lt;strong>Autonomous AI&lt;/strong>: Test automation driven entirely by AI, with human oversight.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&amp;ldquo;Most organizations start with assistive AI. But they soon realize its value is limited and try to move to fully AI-led. That shift requires different tools, structures, and mindsets.&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;p>For decision-making leaders of testing teams, the key strategic decisions include:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>Scope of automation&lt;/strong>: Is your team automating existing test cases, or allowing AI to take full charge of creating, executing, and maintaining test scripts?&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Integration requirements&lt;/strong>: How will AI testing integrate with your existing CI/CD pipelines and development workflows?&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Success metrics&lt;/strong>: Which KPIs will be used to measure success (such as test coverage, execution time, defect detection, and so on)?&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Risk assessment&lt;/strong>: Which applications or features are best suited as the initial targets for AI testing implementation?&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Action recommendation&lt;/strong>: Before evaluating tools, be sure to define your AI testing vision, scope, and success criteria.&lt;/p>
&lt;h2 id="phase-2-days-16-30---redefine-qa-roles-and-test-inputs">Phase 2 (Days 16-30) - Redefine QA Roles and Test Inputs
&lt;/h2>&lt;p>AI test automation does not eliminate existing roles; rather, it transforms them.&lt;/p>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th>&lt;strong>Traditional Role&lt;/strong>&lt;/th>
&lt;th>&lt;strong>AI-Augmented Role&lt;/strong>&lt;/th>
&lt;th>&lt;strong>Key Responsibilities&lt;/strong>&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>Manual Tester&lt;/td>
&lt;td>Prompt Engineer&lt;/td>
&lt;td>Create effective test prompts, review AI-generated tests&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Automation Engineer&lt;/td>
&lt;td>AI Testing Lead&lt;/td>
&lt;td>Oversee the generation, execution, and maintenance of AI tests&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>QA Manager&lt;/td>
&lt;td>AI Testing Strategist&lt;/td>
&lt;td>Define AI testing strategy, measure ROI, optimize processes&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;blockquote>
&lt;p>&amp;ldquo;People often think AI means job losses. That is not the case. What it really does is redeploy testers—manual testers become prompt engineers, and automation engineers become supervisors of AI work.&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;h3 id="expand-test-input-sources">&lt;strong>Expand Test Input Sources&lt;/strong>
&lt;/h3>&lt;p>AI testing platforms can generate comprehensive test cases from a variety of inputs, including:&lt;/p>
&lt;ul>
&lt;li>Jira tickets and user stories&lt;/li>
&lt;li>Screen recordings of application usage&lt;/li>
&lt;li>Natural language requirements&lt;/li>
&lt;li>API specifications and documentation&lt;/li>
&lt;li>Existing manual test cases&lt;/li>
&lt;/ul>
&lt;p>This flexibility means AI testing does not need to strictly adhere to a BDD framework or a specific test case format, making AI testing accessible to teams at every maturity level.&lt;/p>
&lt;h2 id="phase-3-days-31-45---evaluate-ai-testing-tools">Phase 3 (Days 31-45) - Evaluate AI Testing Tools
&lt;/h2>&lt;p>Choosing the right AI testing tool requires aligning it with your infrastructure, team skills, and long-term vision.&lt;/p>
&lt;h3 id="core-capabilities-of-enterprise-ai-testing-platforms">&lt;strong>Core Capabilities of Enterprise AI Testing Platforms&lt;/strong>
&lt;/h3>&lt;ul>
&lt;li>&lt;strong>Open-source test code generation&lt;/strong>: Generates maintainable code in standard frameworks (such as Playwright, Selenium, and so on).&lt;/li>
&lt;li>&lt;strong>Self-healing capability&lt;/strong>: Automatically adapts to user interface (UI) changes without human intervention.&lt;/li>
&lt;li>&lt;strong>Comprehensive test support&lt;/strong>: Covers functional, visual, performance, and security testing.&lt;/li>
&lt;li>&lt;strong>Enterprise integration&lt;/strong>: Works with your CI/CD pipelines, test management, and defect tracking systems.&lt;/li>
&lt;li>&lt;strong>Cross-platform testing&lt;/strong>: Supports web, mobile, API, and enterprise applications (such as Salesforce, SAP, and so on).&lt;/li>
&lt;li>&lt;strong>Visual testing&lt;/strong>: AI-driven visual comparison and anomaly detection.&lt;/li>
&lt;li>&lt;strong>Flaky test management&lt;/strong>: Automatically identifies and resolves inconsistent tests.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&amp;ldquo;Even if you stop using a particular vendor, you still have a code project you can maintain. No black box, no vendor lock-in.&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;p>&lt;strong>Decision framework&lt;/strong>: Evaluate tools against your specific needs, existing infrastructure, and team capabilities. Give priority to platforms that generate standard, maintainable test code rather than proprietary formats.&lt;/p>
&lt;h2 id="phase-4-days-46-60---train-for-new-ai-augmented-testing-roles">Phase 4 (Days 46-60) - Train for New AI-Augmented Testing Roles
&lt;/h2>&lt;p>Introducing AI into test automation brings new AI capabilities and responsibilities, elevating the role of the QA team.&lt;/p>
&lt;h3 id="key-skills-for-the-ai-testing-era">&lt;strong>Key Skills for the AI Testing Era&lt;/strong>
&lt;/h3>&lt;ul>
&lt;li>&lt;strong>Prompt engineering&lt;/strong>: Creating effective test prompts to generate comprehensive test coverage.&lt;/li>
&lt;li>&lt;strong>AI test review&lt;/strong>: Evaluating and refining AI-generated test scripts.&lt;/li>
&lt;li>&lt;strong>Test maintenance management&lt;/strong>: Overseeing self-healing capabilities and test stability.&lt;/li>
&lt;li>&lt;strong>Test prioritization&lt;/strong>: Determining which tests deliver the highest value in each release.&lt;/li>
&lt;li>&lt;strong>Exploratory testing&lt;/strong>: Concentrating human creativity on edge cases and complex scenarios.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&amp;ldquo;The old skills were scripting and debugging. The new skills? Writing prompts, reviewing AI suggestions, and managing code at scale.&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;h3 id="training-resources-for-the-qa-team">&lt;strong>Training Resources for the QA Team&lt;/strong>:
&lt;/h3>&lt;ul>
&lt;li>Internal workshops on AI testing concepts and prompt engineering.&lt;/li>
&lt;li>Vendor-provided training on specific AI testing platforms.&lt;/li>
&lt;li>Hands-on practice in real application testing scenarios.&lt;/li>
&lt;li>Cross-training between manual and automation testers.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Leadership focus&lt;/strong>: Encourage experimentation and create a learning environment where the team can develop AI testing expertise through real-world application.&lt;/p>
&lt;h2 id="phase-5-days-61-75---pilot-and-expand-ai-testing-coverage">Phase 5 (Days 61-75) - Pilot and Expand AI Testing Coverage
&lt;/h2>&lt;p>Launch a focused pilot project using 10-20 test scenarios to achieve fast, measurable impact and build confidence in AI testing capabilities.&lt;/p>
&lt;h3 id="ideal-pilot-project-characteristics">&lt;strong>Ideal Pilot Project Characteristics&lt;/strong>:
&lt;/h3>&lt;ul>
&lt;li>An application of moderate complexity with a stable UI.&lt;/li>
&lt;li>Existing manual test cases for comparison.&lt;/li>
&lt;li>A regular release cadence to demonstrate CI/CD integration.&lt;/li>
&lt;li>A mix of regression, functional, and visual testing needs.&lt;/li>
&lt;li>Stakeholders who are open to innovation and process change.&lt;/li>
&lt;/ul>
&lt;h3 id="implementation-checklist">&lt;strong>Implementation Checklist&lt;/strong>:
&lt;/h3>&lt;ul>
&lt;li>Select the pilot application and define the test scope.&lt;/li>
&lt;li>Configure the AI testing tool and integrate with CI/CD.&lt;/li>
&lt;li>Create initial test prompts and generate baseline tests.&lt;/li>
&lt;li>Execute tests across multiple environments.&lt;/li>
&lt;li>Measure results against traditional testing methods.&lt;/li>
&lt;li>Document lessons learned and optimization opportunities.&lt;/li>
&lt;/ul>
&lt;p>This phase is ideal for expanding test coverage across browsers, devices, and languages—leveraging the multilingual capabilities of AI models to efficiently test international applications.&lt;/p>
&lt;h2 id="phase-6-days-76-90---measure-kpis-and-optimize">Phase 6 (Days 76-90) - Measure KPIs and Optimize
&lt;/h2>&lt;p>Track key performance indicators (KPIs) to quantify the impact of AI testing implementation and uncover optimization opportunities.&lt;/p>
&lt;h3 id="key-ai-testing-metrics">&lt;strong>Key AI Testing Metrics&lt;/strong>:
&lt;/h3>&lt;ul>
&lt;li>&lt;strong>Release time&lt;/strong>: Reduction in overall test cycle time.&lt;/li>
&lt;li>&lt;strong>Test coverage&lt;/strong>: Increase in functional and platform coverage.&lt;/li>
&lt;li>&lt;strong>Maintenance effort&lt;/strong>: Reduction in test script maintenance time.&lt;/li>
&lt;li>&lt;strong>Defect detection&lt;/strong>: Increase in the defect identification rate.&lt;/li>
&lt;li>&lt;strong>Resource utilization&lt;/strong>: The QA team shifting focus to higher-value activities.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&amp;ldquo;Most leaders think AI testing is about cutting costs. But the biggest ROI is actually faster time to market.&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;h3 id="continuous-improvement-framework">&lt;strong>Continuous Improvement Framework&lt;/strong>:
&lt;/h3>&lt;ul>
&lt;li>Review AI testing performance and accuracy weekly.&lt;/li>
&lt;li>Refine prompts based on test results and missed scenarios.&lt;/li>
&lt;li>Extend AI testing to other applications and test types.&lt;/li>
&lt;li>Document best practices and share them across teams.&lt;/li>
&lt;li>Establish an AI testing center of excellence.&lt;/li>
&lt;/ul>
&lt;p>These insights will support your team in making data-driven decisions about test coverage, release readiness, and quality improvement.&lt;/p>
&lt;h2 id="summary---your-90-day-ai-testing-implementation-roadmap">Summary - Your 90-Day AI Testing Implementation Roadmap
&lt;/h2>&lt;table>
&lt;thead>
&lt;tr>
&lt;th>&lt;strong>Phase&lt;/strong>&lt;/th>
&lt;th>&lt;strong>Timeline&lt;/strong>&lt;/th>
&lt;th>&lt;strong>Focus&lt;/strong>&lt;/th>
&lt;th>&lt;strong>Key Deliverables&lt;/strong>&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>1&lt;/td>
&lt;td>Days 1-15&lt;/td>
&lt;td>Strategy definition&lt;/td>
&lt;td>AI testing vision, implementation approach, success metrics&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>2&lt;/td>
&lt;td>Days 16-30&lt;/td>
&lt;td>Role transformation&lt;/td>
&lt;td>Updated team structure, skill requirements, input sources&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>3&lt;/td>
&lt;td>Days 31-45&lt;/td>
&lt;td>Tool selection&lt;/td>
&lt;td>AI testing platform evaluation, selection criteria, proof of concept&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>4&lt;/td>
&lt;td>Days 46-60&lt;/td>
&lt;td>Team training&lt;/td>
&lt;td>Skill development plan, training resources, knowledge sharing&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>5&lt;/td>
&lt;td>Days 61-75&lt;/td>
&lt;td>Pilot implementation&lt;/td>
&lt;td>Initial AI test suite, CI/CD integration, baseline metrics&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>6&lt;/td>
&lt;td>Days 76-90&lt;/td>
&lt;td>Measurement and optimization&lt;/td>
&lt;td>Performance analysis, optimization plan, scaling strategy&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;h2 id="the-future-of-qa---ai-driven-testing-leadership">The Future of QA - AI-Driven Testing Leadership
&lt;/h2>&lt;p>With the right AI testing strategy, your QA organization will not only keep pace with the industry but will lead the transformation toward faster, more reliable software delivery. You are not merely automating tests; you are empowering your team to enhance and streamline the entire testing lifecycle, delivering higher-quality software at unprecedented speed while reducing risk and technical debt. Embrace AI testing now, and you will position your organization at the forefront of quality engineering, creating a sustainable competitive advantage through superior software quality and accelerated innovation.&lt;/p></description></item><item><title>The 5P Method for Effective Meetings - Stop Meetings from Stealing Your Time</title><link>https://chengxiaqiucao.github.io/en/post/078-%E4%BC%9A%E8%AE%AE5p/</link><pubDate>Tue, 15 Apr 2025 00:00:00 +0000</pubDate><guid>https://chengxiaqiucao.github.io/en/post/078-%E4%BC%9A%E8%AE%AE5p/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/078-%E4%BC%9A%E8%AE%AE5p/snap_20250515.webp" alt="Featured image of post The 5P Method for Effective Meetings - Stop Meetings from Stealing Your Time" />&lt;h2 id="introduction">Introduction
&lt;/h2>&lt;blockquote>
&lt;p>&amp;ldquo;Every day is packed with endless meetings! More than half the time is spent listening to a few people arguing!&amp;rdquo;
&amp;ldquo;They love pulling a huge crowd into every meeting, yet hardly anyone actually speaks up!&amp;rdquo;
&amp;ldquo;A single requirement change, and a meeting planned for 10 minutes drags on for two hours!&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;p>In fast-paced software development, meetings are an indispensable part of information sharing, decision making, and problem solving. Yet what we often experience is how inefficient they are! According to statistics, a software engineer spends an average of &lt;strong>12 hours&lt;/strong> per week in various meetings, but &lt;strong>60% of those meetings are proven to be inefficient or even useless&lt;/strong> .&lt;/p>
&lt;p>How can we make meetings a genuine collaboration tool rather than a time sink? In this article, by introducing the 5P method for effective meetings, we will break down the core logic of making meetings more efficient and escape the &amp;ldquo;sea of meetings&amp;rdquo;!&lt;/p>
&lt;h2 id="what-is-the-5p-method">What Is the 5P Method?
&lt;/h2>&lt;p>The 5P method for meetings is essentially the five main aspects we need to focus on when holding a meeting. Handle these five aspects well, and meetings will not sink into the mire of being aimless, lengthy, and inefficient.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/078-%E4%BC%9A%E8%AE%AE5p/snap_20250515_hu_2ea5b9723e2dc6e5.webp"
width="1024"
height="638"
srcset="https://chengxiaqiucao.github.io/post/078-%E4%BC%9A%E8%AE%AE5p/snap_20250515_hu_1d1d3c78534d6bbe.webp 480w, https://chengxiaqiucao.github.io/post/078-%E4%BC%9A%E8%AE%AE5p/snap_20250515_hu_2ea5b9723e2dc6e5.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="160"
data-flex-basis="385px"
>
&lt;/p>
&lt;h2 id="people---who-should-attend">People - Who Should Attend?
&lt;/h2>&lt;blockquote>
&lt;p>Case - In a requirements clarification meeting, only the product manager and a few core developers took part, while testers and UI/UX designers were absent. As a result, during development it was discovered that the understanding of the requirements did not match testing expectations, and the UI/UX design also deviated from the implemented features, leading to a large amount of rework later.&lt;/p>&lt;/blockquote>
&lt;p>One of the most common problems with inefficient meetings is that &amp;ldquo;the people who should be there aren&amp;rsquo;t, while a crowd of people who shouldn&amp;rsquo;t be are.&amp;rdquo; So making sure all key and necessary stakeholders are invited, while avoiding the participation of irrelevant people, is the first step to a successful meeting.&lt;/p>
&lt;p>Focus on the following points:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Necessity:&lt;/strong> Only invite those who can provide key information, participate in decisions, or are directly affected by the meeting outcomes.&lt;/li>
&lt;li>&lt;strong>Representation:&lt;/strong> If the team is large, invite representatives from each function to attend.&lt;/li>
&lt;li>&lt;strong>Clear roles:&lt;/strong> Clarify each person&amp;rsquo;s speaking priorities and responsibilities.&lt;/li>
&lt;/ul>
&lt;p>For example, in the requirements clarification meeting above, we can identify the following People roles to attend:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Product Owner:&lt;/strong> Explain the requirements background, user stories, and business value.&lt;/li>
&lt;li>&lt;strong>Development Team Lead/Members:&lt;/strong> Ask questions from a technical implementation perspective and assess feasibility.&lt;/li>
&lt;li>&lt;strong>Test Lead/QA Engineer:&lt;/strong> Ask questions from a testability perspective and think through test scenarios.&lt;/li>
&lt;li>&lt;strong>UI/UX Designer:&lt;/strong> Clarify the details of user interaction and interface design.&lt;/li>
&lt;li>&lt;strong>(Optional) Architect:&lt;/strong> If the requirements involve complex system architecture changes.&lt;/li>
&lt;/ul>
&lt;h2 id="purpose---why-are-we-holding-this-meeting">Purpose - Why Are We Holding This Meeting?
&lt;/h2>&lt;blockquote>
&lt;p>Case - An agile retrospective turned into a &amp;ldquo;gripe session&amp;rdquo; or a &amp;ldquo;praise session&amp;rdquo;; everyone chimed in, but nobody focused on how to improve the workflow and collaboration for the next iteration. The meeting was held, yet by the next iteration the existing problems still had not improved.&lt;/p>&lt;/blockquote>
&lt;p>A meeting without a goal is like a lone boat at sea that has lost its navigation; it easily loses its bearing, with no guarantee of where it will end up, and ultimately fizzles out.&lt;/p>
&lt;p>Only when every participant understands the meeting&amp;rsquo;s purpose can everyone&amp;rsquo;s understanding be aligned and the discussion be kept from drifting off the main topic.&lt;/p>
&lt;p>And when setting the goal here, a few things should be kept in mind:&lt;/p>
&lt;ul>
&lt;li>Goals should be specific, measurable, achievable, relevant, and time-bound (&lt;strong>SMART principle&lt;/strong>).&lt;/li>
&lt;li>Try to focus a single meeting on 1-2 core goals, avoiding too many topics that cause loss of focus.&lt;/li>
&lt;li>Make sure all participants share a common understanding of the meeting goals.&lt;/li>
&lt;/ul>
&lt;p>For example, for the iteration retrospective above, we can make the goals explicit:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Primary goal:&lt;/strong> Review what went well and what had problems in the previous iteration, and define concrete improvement measures for the next iteration.&lt;/li>
&lt;li>&lt;strong>Specific sub-goals:&lt;/strong>
&lt;ul>
&lt;li>Identify the 1-2 obstacles that most affect team efficiency and work out solutions;&lt;/li>
&lt;li>Identify one good practice that should be maintained.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h2 id="process---how-should-the-meeting-be-run">Process - How Should the Meeting Be Run?
&lt;/h2>&lt;blockquote>
&lt;p>Case - A test case review meeting. Only after the meeting started did everyone receive a thick stack of printed test cases, reading them one by one and raising questions on the spot. The presenter&amp;rsquo;s explanation lacked focus, and reviewers&amp;rsquo; thoughts wandered, causing the meeting to run seriously overtime with extremely poor review results.&lt;/p>&lt;/blockquote>
&lt;p>If Purpose is about keeping the right heading, then Process is the nautical chart for the ship of the meeting. A clear process guides the meeting in an orderly way, ensures every topic is fully discussed, and reaches the goals within the scheduled time.&lt;/p>
&lt;p>This includes agreements on the agenda, time allocation, discussion rules, decision-making methods, and so on.&lt;/p>
&lt;p>Using the case above again, we can agree on the Process before the meeting:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Structured agenda:&lt;/strong>
&lt;ol>
&lt;li>&lt;strong>Pre-meeting preparation (5-10 minutes, or completed before the meeting):&lt;/strong> The host briefly states the review scope, goals, and case background. Emphasize that the test cases have been shared in advance and that participants are assumed to have read them beforehand.&lt;/li>
&lt;li>&lt;strong>Discussion of key/doubtful cases (30-40 minutes):&lt;/strong> Focus the discussion on questions collected in advance or cases flagged as important. Set a time limit for discussing each complex case.&lt;/li>
&lt;li>&lt;strong>Summary and confirmation (10-15 minutes):&lt;/strong> Consolidate review comments, clarify who is responsible for changes and the deadlines. Confirm whether consensus has been reached on test coverage.&lt;/li>
&lt;/ol>
&lt;/li>
&lt;li>&lt;strong>Clear discussion rules:&lt;/strong> For example, encourage constructive opinions, avoid interrupting speakers, and define how to decide when opinions differ (such as majority rule, or a final decision by a specific role).&lt;/li>
&lt;li>&lt;strong>Time control:&lt;/strong> Set an estimated time for each agenda item and enforce it strictly.&lt;/li>
&lt;/ul>
&lt;h2 id="product---what-are-the-outcomes-of-the-meeting">Product - What Are the Outcomes of the Meeting?
&lt;/h2>&lt;blockquote>
&lt;p>Case - A release planning meeting. During the meeting, everyone discussed many feature ideas and potential risks for the new version, but no clear release scope, priorities, or owners were established. After the meeting, people were still vague about &amp;ldquo;which features the new version should actually include.&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;p>First, let us clear up a misconception: a meeting does not count as having produced output simply because it is over and meeting minutes have been generated.
The real outcome of a meeting should be a consensus that can be translated into next actions, and one that is traceable. It can be a decision, an action plan, a solution, a record of consensus, updated documents, and so on. Without a clear deliverable, the meeting is effectively a waste.&lt;/p>
&lt;p>For the case above, clear deliverables could be:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Confirmed release scope:&lt;/strong> A clear Features List or set of User Stories, with priorities distinguished.&lt;/li>
&lt;li>&lt;strong>Preliminary timeline:&lt;/strong> Key milestones and the estimated release date.&lt;/li>
&lt;li>&lt;strong>Clear division of responsibilities:&lt;/strong> An owner for each major module or task.&lt;/li>
&lt;li>&lt;strong>Identified risks and responses:&lt;/strong> Document potential risks and initial mitigation plans.&lt;/li>
&lt;li>&lt;strong>Meeting minutes:&lt;/strong> Include all of the above and specify follow-up items. It is the written record of the meeting outcomes&lt;/li>
&lt;/ul>
&lt;h2 id="pitfall---what-risks-are-anticipated">Pitfall - What Risks Are Anticipated?
&lt;/h2>&lt;p>&lt;strong>Pitfall&lt;/strong> refers to &amp;ldquo;what potential problems or obstacles might arise during the meeting, and how do we prevent or respond to them?&amp;rdquo;&lt;/p>
&lt;h3 id="common-meeting-risks-and-how-to-address-them">Common Meeting Risks and How to Address Them
&lt;/h3>&lt;ul>
&lt;li>
&lt;p>&lt;strong>Topics sprawl and the discussion goes off track:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Pitfall:&lt;/strong> Participants may dig too deeply into a certain detail or bring in unrelated topics.&lt;/li>
&lt;li>&lt;strong>Response (combining Purpose &amp;amp; Process):&lt;/strong> The host should keep the meeting&amp;rsquo;s core goal in mind at all times and gently steer the discussion back on track. A &amp;ldquo;Parking Lot&amp;rdquo; mechanism can be set up to note points that come up on the spur of the moment but are unrelated to the current topic, to be discussed after the meeting.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Key people absent or late:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Pitfall:&lt;/strong> Core decision makers or information providers fail to join on time, so the meeting cannot move forward effectively.&lt;/li>
&lt;li>&lt;strong>Response (combining People):&lt;/strong> Confirm the time with key people in advance and send meeting reminders. If someone is absent at the last minute, assess whether to continue, adjust the agenda, or reschedule the meeting.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>A few people dominate the conversation while others stay silent:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Pitfall:&lt;/strong> This can lead to incomplete information and biased decisions.&lt;/li>
&lt;li>&lt;strong>Response (combining Process):&lt;/strong> The host should consciously invite silent participants to speak, or use methods such as round-robin speaking and anonymous opinion collection to ensure everyone has a chance to contribute.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Insufficient preparation and information asymmetry:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Pitfall:&lt;/strong> Participants have not read the materials in advance, so a lot of time in the meeting is spent syncing basic information.&lt;/li>
&lt;li>&lt;strong>Response (combining Purpose &amp;amp; Product):&lt;/strong> Send meeting materials (such as requirements documents, design drafts, and cases to be reviewed) clearly to participants in advance, and explicitly ask them to read and prepare before the meeting.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>No clear action plan or follow-up:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Pitfall:&lt;/strong> The discussion is lively, but nothing is translated into concrete actions, and it ultimately fizzles out.&lt;/li>
&lt;li>&lt;strong>Response (combining Product):&lt;/strong> Before the meeting ends, be sure to summarize action items, owners, and deadlines, and clarify how progress will be tracked afterwards.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;p>In short, thinking through potential risks in advance and preparing response strategies can effectively keep meetings from being interrupted by surprises or derailed, ensuring they run smoothly and achieve their intended goals.&lt;/p>
&lt;h2 id="summary">Summary
&lt;/h2>&lt;p>Through the case-based introduction of the 5P method above, to run a meeting efficiently, the 5P method can effectively keep it from getting out of control. Its core logic is actually this:&lt;/p>
&lt;p>&lt;strong>&amp;ldquo;Use structured methods to counter the randomness of human nature&amp;rdquo;&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>&lt;strong>People (the right attendees):&lt;/strong> Make sure the right people are in the room.&lt;/li>
&lt;li>&lt;strong>Purpose (a clear goal):&lt;/strong> Be clear about why we are here and where we are going.&lt;/li>
&lt;li>&lt;strong>Process (a clear process):&lt;/strong> Plan the path well and move forward in an orderly way.&lt;/li>
&lt;li>&lt;strong>Product (the expected output):&lt;/strong> Leave with results.&lt;/li>
&lt;li>&lt;strong>Pitfall (anticipated risks):&lt;/strong> Avoid obstacles and arrive smoothly.&lt;/li>
&lt;/ul>
&lt;p>In my earlier articles about the four agile meetings, the related practices also reflect the core logic of the 5P method, and I recommend reading them for reference~&lt;/p></description></item><item><title>Ten Misconceptions That Make Testers Harm Quality</title><link>https://chengxiaqiucao.github.io/en/post/071-%E6%B5%8B%E8%AF%95%E4%BA%BA%E5%91%98%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F%E7%9A%84%E5%8D%81%E5%A4%A7%E8%AF%AF%E5%8C%BA/</link><pubDate>Fri, 28 Mar 2025 15:59:08 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/071-%E6%B5%8B%E8%AF%95%E4%BA%BA%E5%91%98%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F%E7%9A%84%E5%8D%81%E5%A4%A7%E8%AF%AF%E5%8C%BA/</guid><description>&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/071-%E6%B5%8B%E8%AF%95%E4%BA%BA%E5%91%98%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F%E7%9A%84%E5%8D%81%E5%A4%A7%E8%AF%AF%E5%8C%BA/%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F10%E5%A4%A7%E8%AF%AF%E5%8C%BA_hu_81658b60c7e81318.webp"
width="1024"
height="436"
srcset="https://chengxiaqiucao.github.io/post/071-%E6%B5%8B%E8%AF%95%E4%BA%BA%E5%91%98%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F%E7%9A%84%E5%8D%81%E5%A4%A7%E8%AF%AF%E5%8C%BA/%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F10%E5%A4%A7%E8%AF%AF%E5%8C%BA_hu_d28036d5872caacc.webp 480w, https://chengxiaqiucao.github.io/post/071-%E6%B5%8B%E8%AF%95%E4%BA%BA%E5%91%98%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F%E7%9A%84%E5%8D%81%E5%A4%A7%E8%AF%AF%E5%8C%BA/%E4%BC%A4%E5%AE%B3%E8%B4%A8%E9%87%8F10%E5%A4%A7%E8%AF%AF%E5%8C%BA_hu_81658b60c7e81318.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="234"
data-flex-basis="563px"
>
&lt;/p>
&lt;p>Many companies call the engineers who perform testing QA (quality assurance), but QA and Tester are actually two different roles. Even so, there is no denying that a test engineer&amp;rsquo;s primary responsibility is also oriented toward quality — helping the team improve quality by assessing the state of quality.&lt;/p>
&lt;p>But even so, is a test engineer&amp;rsquo;s work necessarily helpful to quality improvement? In real work, some misconceptions can instead make testers&amp;rsquo; work have a negative impact on quality.&lt;/p>
&lt;p>Here Qiucao has sorted out and summarized ten misconceptions by which testers may harm quality, along with the corresponding correct practices.&lt;/p>
&lt;h2 id="1-testings-job-is-to-find-and-report-bugs-but-not-to-confirm-them">1. Testing&amp;rsquo;s job is to find and report Bugs, but not to confirm them
&lt;/h2>&lt;p>&lt;strong>Misconception: Developers and testers often argue over whether a certain issue should be reported as a Bug. &amp;ldquo;The requirement doesn&amp;rsquo;t ask for it,&amp;rdquo; &amp;ldquo;this issue doesn&amp;rsquo;t affect users,&amp;rdquo; and similar reasons come up all the time. Many testers do stop reporting such issues because of these reasons, and some even check with developers whether they are allowed to file a Bug before reporting it.&lt;/strong>&lt;/p>
&lt;p>This is a misconception that does great harm to quality. The value of testing lies in assessing the state of quality, and the key to assessment is independence. Quality is not about right or wrong, only about good or bad. A behavior not defined in the requirements does not mean it is unwanted; not affecting users does not mean it is a good implementation. Testing stands from the perspective of assessing quality, so pointing out defects or raising suggestions for improvement is part of the job. Developers are responsible for analyzing, confirming, and fixing defects. If developers and testers disagree on the confirmation, the PO, business analysts, or CCB members can arbitrate.&lt;/p>
&lt;p>But for testers, reporting &lt;strong>every&lt;/strong> product behavior that they feel is problematic or of poor quality is a professional obligation. Deliberately or inadvertently hiding or covering up defects is the real harm to product quality.&lt;/p>
&lt;h2 id="2-finding-a-bug-is-only-the-beginning-we-should-also-provide-as-much-context-as-possible-for-fixing-it">2. Finding a Bug is only the beginning; we should also provide as much context as possible for fixing it
&lt;/h2>&lt;p>&lt;strong>Misconception: Some testers think that once they have found a problem and reported it, their work is done, that the subsequent fixing process has nothing to do with them, and that all they need to do is verify it after the fix&lt;/strong>&lt;/p>
&lt;p>Testing is one link in the entire software product development lifecycle, and it ultimately serves the overall quality of the product. The Bug itself, in fact, has no value for the product, because only a Bug that has been resolved helps product quality. From this perspective, although reporting Bugs is a tester&amp;rsquo;s main job, for the product the ultimate goal is to resolve the Bug. So as one part of product development, even though fixing Bugs is not directly the tester&amp;rsquo;s responsibility, we should still provide the necessary support for resolving them.&lt;/p>
&lt;p>This part was discussed in detail in a previous article 【】, which you may refer to if interested.&lt;/p>
&lt;h2 id="3-testing-is-not-just-about-verifying-requirements">3. Testing is not just about verifying requirements
&lt;/h2>&lt;p>&lt;strong>Misconception: Testing only needs to verify that the parts explicitly defined in the requirements are correct; undefined parts need not be tested&lt;/strong>&lt;/p>
&lt;p>This is somewhat related to the first misconception and is the premise of many developer–tester arguments about bugs. In the earlier article 【】 on misconceptions about testing goals, we also mentioned this point: beyond verifying requirements, testing should cover much more exploratory work. Testing is not merely checking.&lt;/p>
&lt;p>Beyond that, here I want to emphasize even more the integrity and systematic nature of the product. Especially in an agile development model, this misconception is easily amplified.&lt;/p>
&lt;p>In agile, the output of an agile iteration is the Increment (product increment), which holds true for development work. But testing work is oriented toward the entire product system and cannot cover only the increment. Requirements are incremental too, so of course testing cannot cover only the requirements of the increment. This is why regression testing is a category that must be included in testing, and it is also the fundamental reason test automation is receiving more and more attention. (For analysis and introductions related to agile, see the earlier agile series.)&lt;/p>
&lt;h2 id="4-testing-is-endless-use-good-steel-on-the-blades-edge">4. Testing is endless; use good steel on the blade&amp;rsquo;s edge
&lt;/h2>&lt;p>&lt;strong>Misconception: To find more Bugs, explore and diverge as much as possible, and exploit the clustering effect of Bugs to discover as many Bugs as possible&lt;/strong>&lt;/p>
&lt;p>Still in the article 【】, we also clarified that the goal of testing is not to find more Bugs either. Moreover, testing is in fact endless; the ultimate purpose of testing is to provide a reliable, complete assessment of the quality state of the whole product or system. And whether this quality state is objective and accurate is not necessarily positively correlated with the number of Bugs.&lt;/p>
&lt;p>While finding as many Bugs as possible, testers also need to recognize that we are systematically assessing quality, yet testing can never be exhaustive. Therefore we must allocate our limited time scientifically, giving priority to high-priority parts — new features, code changes, and high-risk modules are all parts that should be tested first and given key assurance.&lt;/p>
&lt;p>&lt;code>Precision Testing&lt;/code> and &lt;code>Risk-Based Testing (RBT)&lt;/code> are practices under this way of thinking that put our testing resources and time first into the high-value parts.&lt;/p>
&lt;h2 id="5-testing-work-does-not-begin-only-at-the-test-submission-stage-it-starts-as-early-as-product-requirement-discussions">5. Testing work does not begin only at the test-submission stage; it starts as early as product requirement discussions
&lt;/h2>&lt;p>&lt;strong>Misconception: Testing should formally begin only after the product is submitted for testing, and Bugs should also be reported only after submission&lt;/strong>&lt;/p>
&lt;p>Today, the above misconception is of course incorrect, because both &lt;code>shift-left testing&lt;/code> and various testing theories emphasize the importance of early testing involvement.&lt;/p>
&lt;p>But theory is theory; in actual practice, testing usually still really begins only after submission for testing.&lt;/p>
&lt;p>On one hand, in the early stage of a product, testing has a low presence and low participation and is easily overlooked;&lt;/p>
&lt;p>on the other hand, many testing teams are assessed heavily on the number of Bugs, which further erodes the motivation for early testing involvement and makes testers less willing to help the team expose product problems early.&lt;/p>
&lt;p>But from the perspective of product delivery, the later the stage, the higher the cost of fixing a problem. So from a product management standpoint, we should abandon the orientation of assessing by Bug count and guide active early participation by testing. Testing can bring its sensitivity to problems into play, identifying and considering many exceptional scenarios starting from requirement discussions, and helping the team avoid them in advance.&lt;/p>
&lt;h2 id="6-in-design-and-architecture-discussions-testing-should-not-be-invisible">6. In design and architecture discussions, testing should not be invisible
&lt;/h2>&lt;p>&lt;strong>Misconception: Architecture and system design, as well as detailed design, are the development team&amp;rsquo;s tasks; testers need not understand or participate in the discussions and can simply wait until product development is complete and then test against the requirements&lt;/strong>&lt;/p>
&lt;p>Similar to the previous point, &lt;code>shift-left testing&lt;/code> does not merely mean that testers understand requirements better; it also requires testers to participate in design and even coding stages.&lt;/p>
&lt;p>We must return to the goal of testing: to assess the quality state of the product as accurately as possible. And quality is necessarily closely tied to the concrete implementation of the product; the more clearly we understand the implementation details, the more targeted our testing can be, including helping the team avoid quality problems in advance during the design and coding stages.&lt;/p>
&lt;p>Conversely, if design and code are a complete black box, it is very likely that some key test scenarios will be missed and problems will leak through.&lt;/p>
&lt;ul>
&lt;li>Without understanding how load balancing is implemented in a cloud application, verifying only on a single node makes it impossible to catch problems caused by load-balancing failures&lt;/li>
&lt;li>Without understanding the system&amp;rsquo;s caching implementation, it is hard to purposefully construct cache-hit scenarios&lt;/li>
&lt;li>Without understanding the responsive layout implementation of the UI, it is hard to efficiently carry out compatibility testing&lt;/li>
&lt;li>Without understanding the interface&amp;rsquo;s validation mechanism, it is hard to construct effective API test data&lt;/li>
&lt;/ul>
&lt;p>All of the above show that testing should not stay outside the design stage and treat product design as outside the scope of testing, thereby ignoring participation in this stage.&lt;/p>
&lt;h2 id="7-an-independent-test-environment-is-a-prerequisite-for-adequate-testing">7. An independent test environment is a prerequisite for adequate testing
&lt;/h2>&lt;p>&lt;strong>Misconception: Test execution only needs to focus on the product itself; testing can be done on an integration environment or even a development environment without affecting test results&lt;/strong>&lt;/p>
&lt;p>It is true that the object of testing is the product itself. But the test environment is actually a key constraint on whether the product can be tested comprehensively and efficiently.&lt;/p>
&lt;p>In software testing and exploration, using the product usually involves the superposition of many different operations and interactions. And when discovering product problems, an important prerequisite for judging the problem is that the relevant preconditions and associated factors of the product itself are clear and definite. To ensure this, an independent, interference-free test environment is especially necessary. If a development environment is used for testing, developers are simultaneously debugging and making changes on that environment during testing, which not only produces a large number of invalid issues but is also a great waste of resources for testing, problem localization, and the like.&lt;/p>
&lt;p>Beyond that, testing inevitably involves creating various exceptional scenarios, and an independent test environment makes it easier for testers to adjust different test scenarios, such as:&lt;/p>
&lt;ul>
&lt;li>Modifying network configurations to create scenarios such as proxy access, internal and external IPs, and weak networks&lt;/li>
&lt;li>Modifying the system time, triggering scheduled tasks, simulating data for different time periods, and similar scenarios&lt;/li>
&lt;li>Simulating scenarios such as insufficient resources, full disk space, and massive or huge files&lt;/li>
&lt;li>Some limiting factors in the product, enabling Debug mode, different authentication settings, and various configuration changes&lt;/li>
&lt;/ul>
&lt;p>All these tests are built on the foundation of an independent, controllable test environment.&lt;/p>
&lt;h2 id="8-test-automation-code-is-also-a-program-treat-test-code-the-way-you-treat-the-product">8. Test automation code is also a program; treat test code the way you treat the product
&lt;/h2>&lt;p>&lt;strong>Misconception: Writing test automation is simply to replace part of manual test execution; once the automation code is written and can run and cover the relevant cases, that is enough&lt;/strong>&lt;/p>
&lt;p>The purpose of test automation is indeed to replace a great deal of manual testing work and achieve efficiency gains. But implementing test automation is not a one-off deal; it is also a long-term process. Moreover, test automation itself is implemented through program code, and where there is a program there will be bugs, so quality assurance and maintenance of the automation scripts and tools themselves is also an important part of a tester&amp;rsquo;s job.&lt;/p>
&lt;p>It is not the case that writing a runnable automation script means we have &amp;ldquo;done automation.&amp;rdquo; Automation scripts, like software products, should go through a lifecycle of requirements analysis, design, coding, testing, and subsequent maintenance.&lt;/p>
&lt;p>So test automation itself is also a fairly large investment. For the relevant scripts to keep delivering value over the long term and truly achieve the goal of improving execution efficiency, good design and continuous maintenance of the test automation code are indispensable.&lt;/p>
&lt;h2 id="9--cicd-pipelines-are-also-testings-responsibility">9. CI/CD pipelines are also testing&amp;rsquo;s responsibility
&lt;/h2>&lt;p>&lt;strong>Misconception: CI/CD, as infrastructure for many development teams today, is usually built and maintained by dedicated DevOps engineers; as testers, we only need to write the automation scripts for the testing portion&lt;/strong>&lt;/p>
&lt;p>Admittedly, within the entire CI/CD pipeline, the part directly related to testing is mainly test automation. But again: testing, as a member of the whole development process, cannot exist independently of that process. Especially in agile development, the integrity of the team is emphasized even more, and the team as a whole is responsible for the development process.&lt;/p>
&lt;p>Therefore, in the process of establishing, operating, and keeping the CI/CD pipeline flowing, there is no clear notion that testing is only responsible for the test automation stage.&lt;/p>
&lt;p>As professionals with a quality perspective, we can also play a greater role in building the CI/CD pipeline:&lt;/p>
&lt;ul>
&lt;li>Defining quality gates for the flow between stages in the pipeline, reflecting shift-left testing in the CI/CD pipeline&lt;/li>
&lt;li>Controlling and identifying code changes, which is highly significant for precision testing in the testing phase&lt;/li>
&lt;li>Monitoring of development, integration, test, and even online production environments, especially the collection and implementation of many quality-related metrics&lt;/li>
&lt;li>Visualization, including automated test reports and the status presentation of various data tracking&lt;/li>
&lt;/ul>
&lt;h2 id="10-cherish-every-opportunity-to-understand-end-users-usage-scenarios">10. Cherish every opportunity to understand end users&amp;rsquo; usage scenarios
&lt;/h2>&lt;p>&lt;strong>Misconception: As a member of the development team, testing need not proactively engage with end users. Interfacing with users is more the job of the sales, after-sales, and customer service teams&lt;/strong>&lt;/p>
&lt;p>Testing work is oriented toward quality, and the ultimate judge of quality is in fact the end user. So many teams emphasize that testing is the voice of the end user, a role that uses and experiences the product from the user&amp;rsquo;s perspective and discovers problems in advance.&lt;/p>
&lt;p>Therefore, in this sense, testing should actually engage with users more, understanding the different scenarios, demands, and even preferences with which users use the product.&lt;/p>
&lt;p>So, when there is an opportunity to engage with users, testing should be proactive rather than resistant. As testers, there are quite a few such opportunities; make full use of chances to engage with users to enrich our understanding of the industry the product belongs to and apply it to our testing work.&lt;/p>
&lt;ul>
&lt;li>User issue support. When some customer issues fed back to the development team require technical support, testers often need to face customers directly, and this is also a place where we intuitively understand users&amp;rsquo; usage scenarios of the product and the problems they face.&lt;/li>
&lt;li>External testing. Before choosing a product, many users will have acceptance testing for it. These tests are often carried out on the customer&amp;rsquo;s side, but product testers often provide support or perform testing as the product side, which is field testing. This is also a great window for deeply understanding user scenarios&lt;/li>
&lt;li>Customer visits. Some companies arrange visits and interviews with end customers in the early or middle stages of product development, and sometimes invite the development team to participate. Although in most cases roles such as system analysts and architects participate more, testing also takes part in such visits, which is an excellent opportunity to deeply understand product application scenarios at an early stage.&lt;/li>
&lt;li>Industry reports. Besides direct communication with end customers, paying attention to industry reports, news, and trend analyses for the industry the product belongs to is likewise an excellent channel for deeply understanding the industry and users the product serves.&lt;/li>
&lt;/ul>
&lt;hr>
&lt;p>The above is a summary of the ten misconceptions by which testers harm quality; everyone is welcome to discuss and add to them.
In addition, for Qiucao&amp;rsquo;s course on systematically improving testing skills, you can reply with &lt;strong>&amp;ldquo;Outline&amp;rdquo;&lt;/strong> or check the course catalog in the official account menu.&lt;/p></description></item><item><title>Musk's Weekly Report Mandate and What Weekly Reports Really Are</title><link>https://chengxiaqiucao.github.io/en/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/</link><pubDate>Fri, 28 Feb 2025 17:20:23 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/Pasted-20250228-1.webp" alt="Featured image of post Musk's Weekly Report Mandate and What Weekly Reports Really Are" />&lt;h2 id="introduction">Introduction
&lt;/h2>&lt;p>One of the hottest topics online these past couple of days has to be Musk&amp;rsquo;s new DOGE policy — the now-famous &amp;ldquo;what did you do last week&amp;rdquo; email requiring every federal employee to send a weekly report listing the five things they did last week, cc&amp;rsquo;ing their supervisor! Miss it twice in a row and it&amp;rsquo;s treated as a resignation!&lt;/p>
&lt;p>And by now more than 1 million U.S. civil servants have already sent this weekly report! 😂😂😂&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/Pasted-20250228-1_hu_15914d90a2dc9cb.webp"
width="1024"
height="445"
srcset="https://chengxiaqiucao.github.io/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/Pasted-20250228-1_hu_fb6c0b0c0841a906.webp 480w, https://chengxiaqiucao.github.io/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/Pasted-20250228-1_hu_15914d90a2dc9cb.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="230"
data-flex-basis="552px"
>
&lt;/p>
&lt;p>As corporate wage slaves, we know this routine all too well — but come to think of it, &lt;strong>why do weekly reports even exist&lt;/strong>?&lt;/p>
&lt;h2 id="what-is-the-essence-of-the-weekly-or-daily-report">What Is the Essence of the Weekly (or Daily) Report?
&lt;/h2>&lt;p>For these U.S. civil servants, writing a weekly report may still be something of a novelty, but for a business-born boss like Musk, weekly reports are a long-standing favorite — he rolled out similar policies at Tesla and Twitter years ago.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/Pasted-20250228_hu_f10e1c34ec2f890f.webp"
width="1024"
height="821"
srcset="https://chengxiaqiucao.github.io/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/Pasted-20250228_hu_b5bb4f277c08c548.webp 480w, https://chengxiaqiucao.github.io/post/062-%E9%A9%AC%E6%96%AF%E5%85%8B%E6%96%B0%E6%94%BF%E7%9C%8B%E5%91%A8%E6%8A%A5/Pasted-20250228_hu_f10e1c34ec2f890f.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="124"
data-flex-basis="299px"
>
&lt;/p>
&lt;p>So why, from a company&amp;rsquo;s or a boss&amp;rsquo;s point of view, do they want to see employees&amp;rsquo; weekly reports?&lt;/p>
&lt;p>Take a software testing department as an example; the value of a weekly report mainly shows up in the following areas:&lt;/p>
&lt;ol>
&lt;li>Risk control&lt;/li>
&lt;/ol>
&lt;p>This should be the part every Leader cares about most in a weekly report. Through weekly reports, you can know the overall progress of the whole project and get a grip on overall quality risks — such as testing delays or insufficient quality exposure. The weekly-report level, unlike a daily report, isn&amp;rsquo;t overly detailed, so it&amp;rsquo;s a good input for keeping a handle on the overall status.&lt;/p>
&lt;ol start="2">
&lt;li>Resource optimization&lt;/li>
&lt;/ol>
&lt;p>By aggregating and analyzing weekly-report data, a Leader can also grasp how much effort every member is putting in, making it easier to dynamically allocate testing resources.&lt;/p>
&lt;p>And this is also the focus of all the attention on Musk&amp;rsquo;s new policy, because the result the weekly reports point to is that underworked federal employees may get fired 🤪🤪&lt;/p>
&lt;ol start="3">
&lt;li>Decision basis&lt;/li>
&lt;/ol>
&lt;p>A weekly report usually also contains some quantitative metrics, such as testing progress, defect data, coverage, escape rate, external support, and other quality data that can be captured or actively reported. These data quantify the current quality state and present it visually, serving as important support for decision-making.&lt;/p>
&lt;h2 id="how-should-testers-write-a-weekly-report">How Should Testers Write a Weekly Report?
&lt;/h2>&lt;p>So as a test engineer, if we&amp;rsquo;re going to send a weekly report, what should it usually contain?&lt;/p>
&lt;p>Here is a weekly-report example from an employee working on IoT software (a smart band):&lt;/p>
&lt;div class="highlight">&lt;div class="chroma">
&lt;table class="lntable">&lt;tr>&lt;td class="lntd">
&lt;pre tabindex="0" class="chroma">&lt;code>&lt;span class="lnt"> 1
&lt;/span>&lt;span class="lnt"> 2
&lt;/span>&lt;span class="lnt"> 3
&lt;/span>&lt;span class="lnt"> 4
&lt;/span>&lt;span class="lnt"> 5
&lt;/span>&lt;span class="lnt"> 6
&lt;/span>&lt;span class="lnt"> 7
&lt;/span>&lt;span class="lnt"> 8
&lt;/span>&lt;span class="lnt"> 9
&lt;/span>&lt;span class="lnt">10
&lt;/span>&lt;span class="lnt">11
&lt;/span>&lt;span class="lnt">12
&lt;/span>&lt;span class="lnt">13
&lt;/span>&lt;span class="lnt">14
&lt;/span>&lt;span class="lnt">15
&lt;/span>&lt;span class="lnt">16
&lt;/span>&lt;span class="lnt">17
&lt;/span>&lt;span class="lnt">18
&lt;/span>&lt;span class="lnt">19
&lt;/span>&lt;span class="lnt">20
&lt;/span>&lt;span class="lnt">21
&lt;/span>&lt;span class="lnt">22
&lt;/span>&lt;span class="lnt">23
&lt;/span>&lt;span class="lnt">24
&lt;/span>&lt;span class="lnt">25
&lt;/span>&lt;span class="lnt">26
&lt;/span>&lt;span class="lnt">27
&lt;/span>&lt;span class="lnt">28
&lt;/span>&lt;span class="lnt">29
&lt;/span>&lt;span class="lnt">30
&lt;/span>&lt;/code>&lt;/pre>&lt;/td>
&lt;td class="lntd">
&lt;pre tabindex="0" class="chroma">&lt;code class="language-gdscript3" data-lang="gdscript3">&lt;span class="line">&lt;span class="cl">&lt;span class="n">I&lt;/span>&lt;span class="o">.&lt;/span> &lt;span class="n">Weekly&lt;/span> &lt;span class="n">Work&lt;/span> &lt;span class="n">Summary&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">Test&lt;/span> &lt;span class="n">execution&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Completed&lt;/span> &lt;span class="n">iterative&lt;/span> &lt;span class="n">testing&lt;/span> &lt;span class="n">of&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">heart&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">rate&lt;/span> &lt;span class="n">monitoring&lt;/span> &lt;span class="n">module&lt;/span> &lt;span class="n">V2&lt;/span>&lt;span class="o">.&lt;/span>&lt;span class="mi">3&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="n">covering&lt;/span> &lt;span class="mi">10&lt;/span> &lt;span class="n">exercise&lt;/span> &lt;span class="n">scenarios&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="ow">and&lt;/span> &lt;span class="n">found&lt;/span> &lt;span class="mi">2&lt;/span> &lt;span class="n">critical&lt;/span> &lt;span class="n">defects&lt;/span> &lt;span class="p">(&lt;/span>&lt;span class="n">data&lt;/span> &lt;span class="n">delay&lt;/span> &lt;span class="n">exceeding&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">threshold&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="n">monitoring&lt;/span> &lt;span class="n">failure&lt;/span> &lt;span class="n">at&lt;/span> &lt;span class="n">low&lt;/span> &lt;span class="n">battery&lt;/span>&lt;span class="p">)&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Ran&lt;/span> &lt;span class="n">compatibility&lt;/span> &lt;span class="n">testing&lt;/span> &lt;span class="n">on&lt;/span> &lt;span class="n">iOS&lt;/span>&lt;span class="o">/&lt;/span>&lt;span class="n">Android&lt;/span> &lt;span class="n">APP&lt;/span> &lt;span class="n">sync&lt;/span>&lt;span class="p">;&lt;/span> &lt;span class="mi">3&lt;/span> &lt;span class="n">device&lt;/span> &lt;span class="n">models&lt;/span> &lt;span class="p">(&lt;/span>&lt;span class="n">including&lt;/span> &lt;span class="n">older&lt;/span> &lt;span class="n">ones&lt;/span>&lt;span class="p">)&lt;/span> &lt;span class="n">showed&lt;/span> &lt;span class="n">data&lt;/span> &lt;span class="n">loss&lt;/span> &lt;span class="n">issues&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Regression&lt;/span> &lt;span class="n">test&lt;/span> &lt;span class="k">pass&lt;/span> &lt;span class="n">rate&lt;/span> &lt;span class="mi">95&lt;/span>&lt;span class="o">%&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="n">with&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">remaining&lt;/span> &lt;span class="mi">5&lt;/span>&lt;span class="o">%&lt;/span> &lt;span class="n">being&lt;/span> &lt;span class="n">low&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">priority&lt;/span> &lt;span class="n">UI&lt;/span> &lt;span class="n">display&lt;/span> &lt;span class="n">issues&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">Defect&lt;/span> &lt;span class="n">management&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Added&lt;/span> &lt;span class="mi">15&lt;/span> &lt;span class="n">defects&lt;/span> &lt;span class="p">(&lt;/span>&lt;span class="mi">2&lt;/span> &lt;span class="n">urgent&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="mi">5&lt;/span> &lt;span class="n">high&lt;/span> &lt;span class="n">priority&lt;/span>&lt;span class="p">),&lt;/span> &lt;span class="n">closed&lt;/span> &lt;span class="mi">8&lt;/span> &lt;span class="n">defects&lt;/span>&lt;span class="p">;&lt;/span> &lt;span class="mi">3&lt;/span> &lt;span class="n">of&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">remaining&lt;/span> &lt;span class="n">defects&lt;/span> &lt;span class="n">require&lt;/span> &lt;span class="n">joint&lt;/span> &lt;span class="n">fixes&lt;/span> &lt;span class="n">with&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">hardware&lt;/span> &lt;span class="n">team&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">Special&lt;/span> &lt;span class="n">testing&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Completed&lt;/span> &lt;span class="n">stress&lt;/span> &lt;span class="n">testing&lt;/span> &lt;span class="n">of&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">OTA&lt;/span> &lt;span class="n">upgrade&lt;/span> &lt;span class="n">process&lt;/span>&lt;span class="p">;&lt;/span> &lt;span class="mi">1&lt;/span> &lt;span class="n">firmware&lt;/span> &lt;span class="n">verification&lt;/span> &lt;span class="n">failure&lt;/span> &lt;span class="n">occurred&lt;/span> &lt;span class="n">after&lt;/span> &lt;span class="n">simulating&lt;/span> &lt;span class="mi">5&lt;/span> &lt;span class="n">consecutive&lt;/span> &lt;span class="n">upgrades&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">In&lt;/span> &lt;span class="n">power&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">consumption&lt;/span> &lt;span class="n">testing&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">standby&lt;/span> &lt;span class="n">power&lt;/span> &lt;span class="n">of&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">sleep&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">monitoring&lt;/span> &lt;span class="n">function&lt;/span> &lt;span class="n">exceeded&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">standard&lt;/span> &lt;span class="n">by&lt;/span> &lt;span class="mi">20&lt;/span>&lt;span class="o">%.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="n">II&lt;/span>&lt;span class="o">.&lt;/span> &lt;span class="n">Core&lt;/span> &lt;span class="n">Issues&lt;/span> &lt;span class="ow">and&lt;/span> &lt;span class="n">Risks&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">Blocking&lt;/span> &lt;span class="n">issues&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">The&lt;/span> &lt;span class="n">heart&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">rate&lt;/span> &lt;span class="n">monitoring&lt;/span> &lt;span class="n">data&lt;/span> &lt;span class="n">delay&lt;/span> &lt;span class="n">defect&lt;/span> &lt;span class="n">creates&lt;/span> &lt;span class="n">a&lt;/span> &lt;span class="n">risk&lt;/span> &lt;span class="n">of&lt;/span> &lt;span class="n">version&lt;/span> &lt;span class="n">release&lt;/span> &lt;span class="n">delay&lt;/span> &lt;span class="ow">and&lt;/span> &lt;span class="n">needs&lt;/span> &lt;span class="n">to&lt;/span> &lt;span class="n">be&lt;/span> &lt;span class="n">fixed&lt;/span> &lt;span class="ow">and&lt;/span> &lt;span class="n">verified&lt;/span> &lt;span class="n">by&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">development&lt;/span> &lt;span class="n">team&lt;/span> &lt;span class="n">within&lt;/span> &lt;span class="mi">48&lt;/span> &lt;span class="n">hours&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="ne">Resource&lt;/span> &lt;span class="n">dependencies&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="n">The&lt;/span> &lt;span class="n">hardware&lt;/span> &lt;span class="n">team&lt;/span>&lt;span class="s1">&amp;#39;s slow response to sensor issues may affect next week&amp;#39;&lt;/span>&lt;span class="n">s&lt;/span> &lt;span class="n">power&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">consumption&lt;/span> &lt;span class="n">test&lt;/span> &lt;span class="n">plan&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="n">III&lt;/span>&lt;span class="o">.&lt;/span> &lt;span class="n">Next&lt;/span> &lt;span class="n">Week&lt;/span>&lt;span class="s1">&amp;#39;s Plan&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Execute&lt;/span> &lt;span class="n">V2&lt;/span>&lt;span class="o">.&lt;/span>&lt;span class="mi">4&lt;/span> &lt;span class="n">feature&lt;/span> &lt;span class="n">testing&lt;/span> &lt;span class="p">(&lt;/span>&lt;span class="n">blood&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">oxygen&lt;/span> &lt;span class="n">monitoring&lt;/span>&lt;span class="p">,&lt;/span> &lt;span class="n">emergency&lt;/span> &lt;span class="n">call&lt;/span>&lt;span class="p">)&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Retest&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">remaining&lt;/span> &lt;span class="n">defects&lt;/span> &lt;span class="ow">and&lt;/span> &lt;span class="n">drive&lt;/span> &lt;span class="n">joint&lt;/span> &lt;span class="n">debugging&lt;/span> &lt;span class="n">with&lt;/span> &lt;span class="n">the&lt;/span> &lt;span class="n">hardware&lt;/span> &lt;span class="n">team&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl"> &lt;span class="o">-&lt;/span> &lt;span class="n">Launch&lt;/span> &lt;span class="n">user&lt;/span>&lt;span class="o">-&lt;/span>&lt;span class="n">scenario&lt;/span> &lt;span class="n">stress&lt;/span> &lt;span class="n">testing&lt;/span> &lt;span class="p">(&lt;/span>&lt;span class="n">simulating&lt;/span> &lt;span class="mi">1&lt;/span>&lt;span class="p">,&lt;/span>&lt;span class="mi">000&lt;/span> &lt;span class="n">devices&lt;/span> &lt;span class="n">uploading&lt;/span> &lt;span class="n">data&lt;/span> &lt;span class="n">concurrently&lt;/span>&lt;span class="p">)&lt;/span>&lt;span class="o">.&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/td>&lt;/tr>&lt;/table>
&lt;/div>
&lt;/div>&lt;p>The weekly report above is summarized from two angles — the project and the testing department — and the value it reflects can be summed up in the table below:&lt;/p>
&lt;table>
&lt;thead>
&lt;tr>
&lt;th>Element&lt;/th>
&lt;th>Value to the Project&lt;/th>
&lt;th>Value to the Testing Department&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>&lt;strong>Test execution progress&lt;/strong>&lt;/td>
&lt;td>Clarifies version quality status and helps the PM assess whether release criteria are met.&lt;/td>
&lt;td>Quantifies team output, making resource allocation and efficiency optimization easier (e.g., adjusting test case priorities).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Defect distribution and trends&lt;/strong>&lt;/td>
&lt;td>Exposes module risks and pushes development to focus on core issues (e.g., a high defect rate in the heart-rate module calls for refactoring).&lt;/td>
&lt;td>Analyzes root causes of defects (code/design/environment) and drives test case library additions and process improvements (e.g., adding low-battery scenarios).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Risks and dependencies&lt;/strong>&lt;/td>
&lt;td>Warns of delay risks and promotes cross-department collaboration (e.g., involving the hardware team).&lt;/td>
&lt;td>Wins support from upper management (e.g., requesting a longer test cycle or more device resources).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Special test results&lt;/strong>&lt;/td>
&lt;td>Validates non-functional requirements (e.g., power consumption, stability), avoiding hard hits to user experience.&lt;/td>
&lt;td>Accumulates performance baseline data to provide a basis for comparison in later versions (e.g., a power-consumption metric library).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Next week&amp;rsquo;s plan and goals&lt;/strong>&lt;/td>
&lt;td>Aligns with project milestones, keeping testing in sync with development (e.g., the blood-oxygen feature test plan matches the iteration schedule).&lt;/td>
&lt;td>Clarifies team division of labor, avoiding overlapping or missed tasks.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;h2 id="summary">Summary
&lt;/h2>&lt;p>So, as an employee, there&amp;rsquo;s really nothing to resist about weekly reports — it&amp;rsquo;s just a perfectly normal management practice.
For testers, the weekly report is both a &amp;ldquo;dashboard&amp;rdquo; for testing work (reflecting quality status in real time) and a &amp;ldquo;bridge&amp;rdquo; for cross-department collaboration (driving problem resolution and resource coordination), while also providing data support for optimizing long-term testing strategy.&lt;/p>
&lt;p>When it all comes down to it, the goal is still &lt;strong>status synchronization&lt;/strong>&lt;/p>
&lt;p>Just like agile stand-ups, and the daily reports that traditional projects may also have, their purpose is actually the same; I&amp;rsquo;ve covered this in detail in earlier posts, so feel free to refer to those.&lt;/p>
&lt;hr></description></item><item><title>How to Handle Conflicts Between Developers and Testers</title><link>https://chengxiaqiucao.github.io/en/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/</link><pubDate>Wed, 19 Feb 2025 12:28:00 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-2.webp" alt="Featured image of post How to Handle Conflicts Between Developers and Testers" />&lt;blockquote>
&lt;p>A reader asked: on a team, developers and testers often run into friction and conflict — how do we avoid such conflicts within the team?&lt;/p>&lt;/blockquote>
&lt;h1 id="the-origin-of-conflict">The Origin of Conflict
&lt;/h1>&lt;p>In a team, conflict between members is actually perfectly normal and very hard to eliminate entirely. The causes vary, but in poor teams conflicts are more likely to arise: mismatched goals and expectations, lack of trust, and poor communication are all common reasons that conflicts arise and even escalate.&lt;/p>
&lt;h1 id="must-conflict-always-be-avoided">Must Conflict Always Be Avoided?
&lt;/h1>&lt;p>From the standpoint of the project and the product, the friction and conflict between developers and testers isn&amp;rsquo;t entirely a bad thing. Nor should we take it for granted that conflict must always be avoided.&lt;/p>
&lt;p>In many R&amp;amp;D project management practices, the conflict between developers and testers is called constructive conflict — that is, this kind of conflict is constructive for improving product quality, and product quality gets improved through the two sides&amp;rsquo; conflict-focused discussions on specific issues.&lt;/p>
&lt;p>This idea in fact aligns with how conflict management classifies conflict types.&lt;/p>
&lt;p>In conflict management theory, using the two dimensions of how important the matter behind the conflict is and the interpersonal relationship, conflict types can be divided into the following four categories:&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-1_hu_9c16675ad641f7d9.webp"
width="1024"
height="786"
srcset="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-1_hu_827295a4fc851e8b.webp 480w, https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-1_hu_9c16675ad641f7d9.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="130"
data-flex-basis="312px"
>
&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>Constructive conflict&lt;/strong>: The conflict is task-related, usually aimed at solving a problem, with little impact on the interpersonal relationship between the two sides. This kind of conflict is actually healthy.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Destructive conflict&lt;/strong>: The conflict is also aimed at solving a problem, but it is more intense and damaging to the relationship, affecting friendly cooperation down the line.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Dysfunctional conflict&lt;/strong>: This one is worse — caused purely by the estrangement between the two sides, with little to do with disagreement over the matter itself; you could call it conflict for conflict&amp;rsquo;s sake.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Functional conflict&lt;/strong>: This is the most common kind, directed at trivial matters and usually showing up as grumbling, joking complaints, and the like.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>For the different conflict types, a team should generally encourage constructive conflict, stop destructive conflict promptly, isolate dysfunctional conflict, and tolerate functional conflict while keeping it from accumulating.&lt;/p>
&lt;h1 id="the-thomas-kilmann-conflict-model">The Thomas-Kilmann Conflict Model
&lt;/h1>&lt;p>For individuals, there is also a theoretical model for how to handle conflict — the Thomas-Kilmann conflict management model:&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220_hu_148e1d87e68b7485.webp"
width="1024"
height="576"
srcset="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220_hu_ab13167beeb5b84a.webp 480w, https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220_hu_148e1d87e68b7485.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="177"
data-flex-basis="426px"
>
&lt;/p>
&lt;p>From two dimensions when facing conflict — your personal assertiveness in solving the problem and your cooperativeness in managing the relationship with the other party — come the following five conflict-handling strategies:&lt;/p>
&lt;p>&lt;strong>Competing&lt;/strong>: When an individual is assertive, they can adopt a competing strategy. It creates a win-or-lose situation, where the stronger party forces the other to accept their demands. &lt;strong>Win-Lose&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Collaborating&lt;/strong>: This is the best strategy — through cooperation and teamwork, both sides find a win-win path where 1+1&amp;gt;2. &lt;strong>Win-Win&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Avoiding&lt;/strong>: Does not solve the problem; a cold treatment that shelves the issue. &lt;strong>Lose-Lose&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Accommodating&lt;/strong>: One side voluntarily yields in order to preserve the relationship. &lt;strong>Lose-Win&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Compromising&lt;/strong>: Meeting in the middle — both sides give a little and make mutual concessions to reach a middle-ground solution, forming a compromise. &lt;strong>Half-Half&lt;/strong>&lt;/p>
&lt;p>Different individuals, when facing conflict, consciously or unconsciously adopt different strategies. Understanding this model helps us assess conflicts more rationally and choose an appropriate way to respond.&lt;/p>
&lt;h1 id="how-should-a-team-manage-conflict">How Should a Team Manage Conflict?
&lt;/h1>&lt;p>For an R&amp;amp;D team, managing conflict well fundamentally comes down to building a strong team culture on the foundation of sound processes and systems, and fostering a transparent, trust-based cooperative relationship and environment.&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Sound systems. For example, disputes over bugs should have an arbitration mechanism, rather than leaving developers and testers to argue themselves red in the face.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Team culture. Testing and development work should not be set against each other; instead, everyone collaborates toward a shared quality goal.&lt;/p>
&lt;/li>
&lt;/ul></description></item><item><title>Should You Tolerate a High Performer with Poor Conduct?</title><link>https://chengxiaqiucao.github.io/en/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/</link><pubDate>Sat, 02 Nov 2024 18:03:14 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/GE-9block.webp" alt="Featured image of post Should You Tolerate a High Performer with Poor Conduct?" />&lt;h2 id="what-is-the-question">What Is the Question
&lt;/h2>&lt;p>Will a boss tolerate an employee with poor conduct? Here, &amp;ldquo;poor conduct&amp;rdquo; can be understood as violating discipline or even the law, disregarding public order and good morals, and so on — in other words, the employee has a problem with values.&lt;/p>
&lt;p>But there is actually another implicit premise here: this employee is presumably very capable (setting aside things like background — though background, of course, is itself a kind of capability). Otherwise there would be no basis for discussing whether to tolerate them at all.&lt;/p>
&lt;h2 id="the-theoretically-correct-approach">The Theoretically Correct Approach
&lt;/h2>&lt;p>Therefore, what we are discussing here is the question of employee evaluation in management. When companies evaluate employees, they usually look at two dimensions in combination: performance and values.&lt;/p>
&lt;h3 id="the-ge-9-box-grid">The GE 9-Box Grid
&lt;/h3>&lt;p>For example, when GE evaluates employees, it combines these two dimensions with three levels — high, medium, and low — to produce a nine-box grid.&lt;/p>
&lt;p>Green: excellent evaluation&lt;/p>
&lt;p>Blue: competent or improvable&lt;/p>
&lt;p>Red: should be eliminated&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/GE-9block_hu_74eb803abc6753cf.webp"
width="1024"
height="574"
srcset="https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/GE-9block_hu_9fad0bdf1ff25d5c.webp 480w, https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/GE-9block_hu_74eb803abc6753cf.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="178"
data-flex-basis="428px"
>
&lt;/p>
&lt;p>Moreover, in this nine-box grid, values actually carry more weight than performance: even with excellent performance, an employee still leans toward red, tending toward elimination.&lt;/p>
&lt;h3 id="alibabas-five-types-of-employees-model">Alibaba&amp;rsquo;s Five Types of Employees Model
&lt;/h3>&lt;p>Similarly, it is said that Alibaba also has a classification of employees into five types.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/ali-5%E7%B1%BB%E5%91%98%E5%B7%A5_hu_11deae8d6c04aa58.webp"
width="1024"
height="808"
srcset="https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/ali-5%E7%B1%BB%E5%91%98%E5%B7%A5_hu_3265bb5b10ab4007.webp 480w, https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/ali-5%E7%B1%BB%E5%91%98%E5%B7%A5_hu_11deae8d6c04aa58.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="126"
data-flex-basis="304px"
>
&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Stars: outstanding performance, prominent contributions, and sound values; performance resources are tilted toward them.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Oxen: diligent and conscientious, fully fulfilling their duties; the bedrock of the team.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Wolves: exceptional ability but problematic values; if they cannot be corrected in time, they must be resolutely replaced.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>White Rabbits: appear hardworking and have good values but lack ability; if they cannot improve, they too must be eliminated.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Dogs: neither ability nor values are up to par; eliminate them resolutely.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>So from the above we can see that mature companies have a fairly clear stance on employees with values problems: no matter how good your performance, you should still be eliminated — that is, poor conduct will not be tolerated.&lt;/p>
&lt;h2 id="possible-real-world-scenarios">Possible Real-World Scenarios
&lt;/h2>&lt;p>The above is more about the theoretically correct approach.&lt;/p>
&lt;p>In reality, however, what choice a boss makes is usually shaped jointly by the stage the company is at and, of course, the boss&amp;rsquo;s own personal values.&lt;/p>
&lt;p>Marx pointed out long ago that &amp;ldquo;capital comes into the world dripping from head to toe, from every pore, with blood and dirt.&amp;rdquo; Of course, this refers more to the stage of primitive capital accumulation, where achieving capital growth often means stopping at nothing. In other words, in the early stages of capital accumulation, poor conduct is, with very high probability, unavoidable.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/%E9%A9%AC%E5%85%8B%E6%80%9D-%E8%B5%84%E6%9C%AC%E5%87%BA%E7%94%9F_hu_8cffab4037386663.webp"
width="1024"
height="511"
srcset="https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/%E9%A9%AC%E5%85%8B%E6%80%9D-%E8%B5%84%E6%9C%AC%E5%87%BA%E7%94%9F_hu_a0c10d9d1d49a795.webp 480w, https://chengxiaqiucao.github.io/post/045-%E6%98%AF%E5%90%A6%E8%A6%81%E5%AE%B9%E5%BF%8D%E5%93%81%E8%A1%8C%E4%B8%8D%E7%AB%AF%E4%BD%86%E4%B8%9A%E7%BB%A9%E4%BC%98%E7%A7%80%E7%9A%84%E5%91%98%E5%B7%A5/%E9%A9%AC%E5%85%8B%E6%80%9D-%E8%B5%84%E6%9C%AC%E5%87%BA%E7%94%9F_hu_8cffab4037386663.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="200"
data-flex-basis="480px"
>
&lt;/p>
&lt;p>So in reality, the logic behind a boss&amp;rsquo;s choice is actually quite simple:&lt;/p>
&lt;p>If the company&amp;rsquo;s survival is the top priority, then delivering results and simply staying alive often matters more to the boss; in this case they will mostly be more tolerant of employees who stop at nothing yet deliver excellent performance.&lt;/p>
&lt;p>But once the company has grown big and strong, continuing to tolerate misconduct may harm its health and long-term development, so naturally it can no longer be tolerated.&lt;/p>
&lt;p>&lt;strong>Of course, we should still believe that there really are entrepreneurs with a grand vision and strong character who have upheld those fine values from the very beginning. It is just that when a company faces life and death, the approach it chooses to adopt is the more convincing one.&lt;/strong>&lt;/p></description></item></channel></rss>