<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quality Management on Testing Observation</title><link>https://chengxiaqiucao.github.io/en/tags/quality-management/</link><description>Recent content in Quality Management on Testing Observation</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>|by Daniel Wei</copyright><lastBuildDate>Wed, 27 Aug 2025 16:31:25 +0800</lastBuildDate><atom:link href="https://chengxiaqiucao.github.io/en/tags/quality-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Shift-Left Testing Is More Than Testers Getting Involved Early</title><link>https://chengxiaqiucao.github.io/en/post/124-testing_shift_left/</link><pubDate>Wed, 27 Aug 2025 16:31:25 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/124-testing_shift_left/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827-1.webp" alt="Featured image of post Shift-Left Testing Is More Than Testers Getting Involved Early" />&lt;h2 id="preface">Preface
&lt;/h2>&lt;p>In the traditional waterfall software development process, testing usually sits late in the SDLC, and testers take on the duty of &amp;ldquo;quality gatekeeper&amp;rdquo;. As agile development, DevOps, and other delivery models have been adopted, rapid iteration and continuous delivery have become the norm, and accordingly the concept of &amp;ldquo;shift-left testing&amp;rdquo; is mentioned frequently; many agile teams treat &amp;ldquo;shift-left testing&amp;rdquo; as an important practice.&lt;/p>
&lt;p>Many teams encourage testers to get involved in projects as early as possible, involving testers in requirements, design, and development, including requirements reviews, design discussions, pairing during development, unit/integration testing, continuous integration pipelines, test automation, and so on.&lt;/p>
&lt;p>In this article we will not discuss these specific practices of shift-left testing, but rather clarify one point: &lt;strong>&amp;ldquo;shift-left testing&amp;rdquo; is not merely testers moving toward the front end&lt;/strong>&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827-1_hu_9f4345ad4f2a000f.webp"
width="1024"
height="552"
srcset="https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827-1_hu_d271f541656de579.webp 480w, https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827-1_hu_9f4345ad4f2a000f.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="185"
data-flex-basis="445px"
>
&lt;/p>
&lt;h2 id="software-quality">Software Quality
&lt;/h2>&lt;p>What is software quality? The definition in &lt;strong>IEEE.1061&lt;/strong> is as follows:&lt;/p>
&lt;blockquote>
&lt;p>Software quality is the degree to which a software product satisfies stated requirements as well as implicit needs arising from user needs and expectations.&lt;/p>&lt;/blockquote>
&lt;p>This definition is quite abstract, and it also shows indirectly that quality is a product attribute that is rather hard to define precisely.&lt;/p>
&lt;p>Roles with different perspectives actually see quality differently.&lt;/p>
&lt;h3 id="user-perspective">User Perspective
&lt;/h3>&lt;p>Quality is the degree to which user needs and expectations are met. That is, can the product help users solve specific problems? Is it convenient and fast? Stable and reliable? Good value for money?&lt;/p>
&lt;p>&amp;ldquo;This software is really easy to use!&amp;rdquo;
&amp;ldquo;This system is very stable and never crashes!&amp;rdquo;
&amp;ldquo;This app feels so smooth~&amp;rdquo;&lt;/p>
&lt;h3 id="developer-perspective">Developer Perspective
&lt;/h3>&lt;p>From a developer&amp;rsquo;s perspective, quality is reflected in the code and architecture.&lt;/p>
&lt;p>&amp;ldquo;Is the code standardized, readable, and maintainable?&amp;rdquo;
&amp;ldquo;Clear architecture, easy to extend&amp;rdquo;
&amp;ldquo;Technical debt is under control&amp;rdquo;&lt;/p>
&lt;h3 id="tester-perspective">Tester Perspective
&lt;/h3>&lt;p>From a tester&amp;rsquo;s perspective, beyond bringing in the user&amp;rsquo;s experience, quality is more about adaptability across multiple scenarios.&lt;/p>
&lt;p>The degree to which the software fits various scenarios such as happy path, angry path, scary path, greedy path, and so on.&lt;/p>
&lt;h3 id="management-perspective">Management Perspective
&lt;/h3>&lt;p>From a management perspective, quality is reflected in whether delivery is on time, whether the budget is under control, and whether product metrics are met.&lt;/p>
&lt;p>&amp;ldquo;The product is delivered on time with high quality&amp;rdquo;
&amp;ldquo;R&amp;amp;D costs are greatly reduced&amp;rdquo;
&amp;ldquo;The system runs stably with 99.999% availability&amp;rdquo;&lt;/p>
&lt;h3 id="business-perspective">Business Perspective
&lt;/h3>&lt;p>From a business operations perspective, quality measures the degree to which the product creates value and competitive advantage.&lt;/p>
&lt;p>&amp;ldquo;User downloads&amp;rdquo;, &amp;ldquo;user registrations&amp;rdquo;, &amp;ldquo;order conversion rate&amp;rdquo;, &amp;ldquo;user retention rate&amp;rdquo;, and so on&amp;hellip;.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827-2_hu_86f84c6df08d616f.webp"
width="1024"
height="561"
srcset="https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827-2_hu_d76a41f015899b10.webp 480w, https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827-2_hu_86f84c6df08d616f.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="182"
data-flex-basis="438px"
>
&lt;code>A thousand Hamlets in a thousand people's eyes&lt;/code> - so it is with quality too!&lt;/p>
&lt;p>In the end, it comes down to what we often stress: quality is not guaranteed by testing, and testing cannot guarantee it either! Quality is closely tied to the whole team and to everyone in the software lifecycle chain; everyone should be an owner!&lt;/p>
&lt;h2 id="the-essence-of-shift-left-testing">The Essence of Shift-Left Testing
&lt;/h2>&lt;p>With the explanation in the previous section, it becomes easy to understand the point of this article&amp;rsquo;s title: &lt;code>&amp;quot;shift-left testing&amp;quot; is not merely testers moving forward!&lt;/code>&lt;/p>
&lt;p>Because of the adoption of rapid iteration and continuous delivery, this quality control measure that emerged accordingly moves testers forward. Although testing-related activities are no longer confined to late-stage verification, if quality still depends on testers&amp;rsquo; activities, it is still treating the symptoms rather than the root cause.&lt;/p>
&lt;p>&lt;strong>Shift-left testing&lt;/strong> is essentially the popularization of an all-hands quality culture. Testers shifting left should, more importantly, bring the testing mindset - uniquely sensitive to quality risks - to the front end, and drive the whole team to build a quality-first cultural atmosphere.&lt;/p>
&lt;p>That is, &lt;strong>testing should transform toward [QA]!&lt;/strong> And the &lt;code>QA&lt;/code> here is not &lt;code>Quality Assurance&lt;/code> in the traditional sense, which focuses on process control and quality assurance work; it should be a new type of QA suited to the agile model.&lt;/p>
&lt;h2 id="testings-transformation-toward-qa">Testing&amp;rsquo;s Transformation Toward QA
&lt;/h2>&lt;h3 id="quality-assurance">Quality Assurance
&lt;/h3>&lt;p>The traditional QA role, &lt;code>Quality Assurance&lt;/code>, is a role dedicated to the quality system and is not the same as the testing role. QA&amp;rsquo;s work is more about formulating and supervising quality standards, with process control across the entire lifecycle; testing, on the other hand, is more of an engineering role based on testing technology.&lt;/p>
&lt;p>With the shift-left trend, testing should no longer be confined to the application of testing technology, but should turn its perspective to &lt;code>Quality Assurance&lt;/code>, paying attention to quality risks at every link in the entire software development chain.&lt;/p>
&lt;h3 id="quality-analyzer">Quality Analyzer
&lt;/h3>&lt;p>That is actually not enough! Shift-left testing is not a role switch; more importantly, it also involves introducing the testing mindset. So at this point, testing should also be a &lt;code>Quality Analyzer&lt;/code>. For example:&lt;/p>
&lt;h4 id="during-requirements-review">During requirements review:
&lt;/h4>&lt;p>&lt;strong>Find the gray areas&lt;/strong>: Proactively identify ambiguities in requirements. For example, &amp;ldquo;the system response should be fast&amp;rdquo; - how fast is fast? &amp;ldquo;A friendly user interface&amp;rdquo; - how is friendly defined?&lt;/p>
&lt;p>&lt;strong>Raise &amp;ldquo;What if&amp;rdquo; questions&lt;/strong>: Explore various scenarios, including normal flows, exception flows, and boundary cases:&lt;/p>
&lt;ul>
&lt;li>&amp;ldquo;What happens if the user enters special characters here?&amp;rdquo;&lt;/li>
&lt;li>&amp;ldquo;If the network suddenly drops, how will the data be handled?&amp;rdquo;&lt;/li>
&lt;li>&amp;ldquo;If the user has no permission, what prompt should be shown?&amp;rdquo;&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Ensure requirements are testable&lt;/strong>: Assess whether each requirement can be verified through concrete operations and expected results&lt;/p>
&lt;h4 id="during-the-architecturedesign-phase">During the architecture/design phase:
&lt;/h4>&lt;p>&lt;strong>Start from the user&amp;rsquo;s perspective&lt;/strong>: Check whether the design&amp;rsquo;s flows are smooth and intuitive&lt;/p>
&lt;p>&lt;strong>Focus on edge cases&lt;/strong>: Whether loading states, error prompts, empty-state pages, etc. have all been designed&lt;/p>
&lt;p>&lt;strong>Assess accessibility&lt;/strong>: Consider whether the design is friendly to all user groups&lt;/p>
&lt;p>&lt;strong>Assess system testability&lt;/strong>: Ensure the system is verifiable, including log recording, traceability of operation flows, third-party mocking, and so on&lt;/p>
&lt;p>&lt;strong>Assess non-functional requirements and test strategy&lt;/strong>: Ensure that the architecture and design phase has fully considered performance, security, reliability, and other non-functional requirements, and build corresponding test plans&lt;/p>
&lt;h4 id="during-development">During development:
&lt;/h4>&lt;p>&lt;strong>Drive unit test coverage&lt;/strong>: Help the development team build unit test frameworks and improve test coverage&lt;/p>
&lt;p>&lt;strong>Go deep into system integration&lt;/strong>: Work with the development team to build a continuous integration CI pipeline based on a suitable branch management model, and build the &lt;code>quality gate&lt;/code> for test automation&lt;/p>
&lt;p>By deeply participating in the front-end links, test thinking and reflection on and keen observation of software quality are integrated into software development activities beyond testing.&lt;/p>
&lt;h3 id="quality-advocator">Quality Advocator
&lt;/h3>&lt;p>In addition, a quality culture does not happen overnight. In a fast-moving team, a role that puts quality first, continuously advocates quality awareness to the team, and can promptly raise &amp;ldquo;objections&amp;rdquo; when quality is at risk of losing control is even more an important function of testers after &amp;ldquo;shift-left testing&amp;rdquo;.&lt;/p>
&lt;p>But for this new function to work, it cannot do without the team&amp;rsquo;s and management&amp;rsquo;s consistent recognition of &lt;strong>quality first&lt;/strong>, including institutional support for testers&amp;rsquo; related work after shifting left. Otherwise, quality first will mostly remain a formality, nothing more than a catchy slogan.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827_hu_fad4a6a43da71da3.webp"
width="1024"
height="471"
srcset="https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827_hu_c51cb5cb08423bdd.webp 480w, https://chengxiaqiucao.github.io/post/124-testing_shift_left/Pasted-20250827_hu_fad4a6a43da71da3.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="217"
data-flex-basis="522px"
>
&lt;/p>
&lt;h2 id="conclusion">Conclusion
&lt;/h2>&lt;p>With the continuous development of agile and DevOps technologies, the speed, rhythm, and complexity of software development keep increasing. In this context, for shift-left testing to be truly implemented, building a quality culture is actually fundamental.&lt;/p>
&lt;p>And in this process, testing also needs to complete its role transformation, moving toward quality consultant, quality analyst, and quality advocator, and delivering value on a broader scale.&lt;/p>
&lt;p>In short, implementing &amp;ldquo;shift-left testing&amp;rdquo; requires integrating quality thinking into every link of development, branding the quality culture into the team&amp;rsquo;s DNA, and ultimately building a quality ecosystem with full participation and continuous improvement.&lt;/p></description></item><item><title>Dare to Be a Dissenter - More on Testers' Perception of Their Role</title><link>https://chengxiaqiucao.github.io/en/post/123-testing_not_valid/</link><pubDate>Wed, 20 Aug 2025 16:01:41 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/123-testing_not_valid/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825-2.webp" alt="Featured image of post Dare to Be a Dissenter - More on Testers' Perception of Their Role" />&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825-2_hu_665c0e470108848e.webp"
width="1024"
height="683"
srcset="https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825-2_hu_5068e2c36faf82e8.webp 480w, https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825-2_hu_665c0e470108848e.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="149"
data-flex-basis="359px"
>
&lt;/p>
&lt;h2 id="preface">Preface
&lt;/h2>&lt;p>A few days ago, I read a &lt;a class="link" href="https://www.ministryoftesting.com/articles/overcoming-the-trap-of-intellectual-conformity-tips-for-software-testers?utm_campaign=Software%2BTesting%2BWeekly&amp;amp;utm_medium=web&amp;amp;utm_source=Software_Testing_Weekly_280" target="_blank" rel="noopener"
>blog post&lt;/a> by the foreign blogger &lt;code>Vitaly Sharovatov&lt;/code>, about the &amp;ldquo;trap of intellectual conformity&amp;rdquo; in enterprises and R&amp;amp;D teams. Because of the &lt;strong>trap of intellectual conformity&lt;/strong>, many avoidable wrong decisions get pushed through. And testers can play a more critical role in this.&lt;/p>
&lt;p>It was quite inspiring to read; after some deep thought, I wrote this article to share with you all~&lt;/p>
&lt;h2 id="the-trap-of-intellectual-conformity">The Trap of Intellectual Conformity
&lt;/h2>&lt;blockquote>
&lt;p>The &lt;strong>trap of intellectual conformity&lt;/strong> refers to the tendency of an individual who holds a certain position or perception to selectively accept information consistent with it while ignoring or overlooking inconsistent information, thereby forming a self-reinforcing cognitive loop that makes it difficult to assess reality objectively.&lt;/p>&lt;/blockquote>
&lt;p>In the 1950s, psychologists such as Festinger, Carlsmith, and Solomon Asch conducted many related experiments, confirming the widespread existence of cognitive conformity bias:&lt;/p>
&lt;ul>
&lt;li>When performing boring tasks, subjects paid less were more likely than those paid more to change their original evaluation, to rationalize the conflict between their behavior and the outcome.&lt;/li>
&lt;li>In another experiment, most subjects changed their originally correct choice because of other people&amp;rsquo;s wrong answers.&lt;/li>
&lt;li>When the same food was priced differently, subjects tended to believe the more expensive food tasted better.&lt;/li>
&lt;/ul>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825-1_hu_4a1882e6ab3fb1d6.webp"
width="1024"
height="684"
srcset="https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825-1_hu_62e2d3a34d3bde29.webp 480w, https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825-1_hu_4a1882e6ab3fb1d6.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="149"
data-flex-basis="359px"
>
&lt;/p>
&lt;p>In short, the experiments above are what we call the &amp;ldquo;&lt;strong>conformity mentality&lt;/strong>&amp;rdquo;&lt;/p>
&lt;h2 id="quality-risks-caused-by-intellectual-conformity">Quality Risks Caused by Intellectual Conformity
&lt;/h2>&lt;p>In enterprises, quality problems caused by the &amp;ldquo;conformity mentality&amp;rdquo; above and going along with the majority opinion are not uncommon.&lt;/p>
&lt;ul>
&lt;li>A development build that cannot even pass smoke testing is hastily submitted for testing, simply because the developers &amp;ldquo;feel&amp;rdquo; it is fine&lt;/li>
&lt;li>A feature that a leader thought up on a whim is rushed into development, and because it does not meet real user needs, it becomes a white elephant or even has to be rolled back&lt;/li>
&lt;li>Without investigation of the user base or analysis of real usage scenarios, a new feature is completely unusable&lt;/li>
&lt;/ul>
&lt;p>For the problems above, did really no one feel beforehand that something might be wrong? It is just that most people had no opinion, or the process reached a certain node, and it was pushed through by default.&lt;/p>
&lt;p>I once saw a view from a startup CEO: software testers are &amp;ldquo;more harmful than helpful&amp;rdquo; in terms of cost-effectiveness. If you hire only excellent developers with quality awareness, you do not need a dedicated quality role.&lt;/p>
&lt;p>But is that really the case? In my earlier articles, I discussed the difference between &amp;ldquo;developer thinking&amp;rdquo; and &amp;ldquo;tester thinking&amp;rdquo;:&lt;/p>
&lt;ul>
&lt;li>Developers tend to pursue &lt;strong>certainty&lt;/strong>. Based on definite requirements and steps, they define how the product should behave.&lt;/li>
&lt;li>Testers need to consider various possible paths and branch scenarios based on &lt;strong>uncertainty&lt;/strong>, and assess the product&amp;rsquo;s possible behavior based on the unknown.&lt;/li>
&lt;/ul>
&lt;p>Moreover, in a performance-driven organization, developers are hired to deliver results, not to question. They are evaluated on their ability to build, not on their ability to find and respond to problems.&lt;/p>
&lt;p>And based on the &lt;strong>trap of intellectual conformity&lt;/strong>, in an output-oriented organization, dissenting voices are continuously weakened, so even &lt;strong>developers with excellent quality awareness&lt;/strong> find it hard to put quality first in such an environment.&lt;/p>
&lt;h2 id="testing-the-dissenter-assigned-by-the-role">Testing, the &amp;ldquo;Dissenter&amp;rdquo; Assigned by the Role
&lt;/h2>&lt;p>Many people with a &amp;ldquo;conformity mentality&amp;rdquo; can actually sense that something is wrong; they just lack the courage to raise a &amp;ldquo;dissent&amp;rdquo;. But once a challenger appears who points out the problem, they too can actively offer opinions.&lt;/p>
&lt;p>And the testing role, by its very design, is assigned and expected to raise questions and challenges.&lt;/p>
&lt;p>This is precisely the necessity for the testing role to exist and matter: lowering the threshold for others to dissent and creating space for critical thinking in the team.&lt;/p>
&lt;p>As testers, we should not confine ourselves to the limits of the development lifecycle; we should actively shift testing left and participate more in earlier phases, so as to better demonstrate the value of the role.&lt;/p>
&lt;p>Of course, recognizing this also means accepting the positioning of being the &amp;ldquo;&lt;strong>bearer of bad news&lt;/strong>&amp;rdquo;. Face it calmly; a team&amp;rsquo;s path to success cannot do without such a role.&lt;/p>
&lt;h2 id="conclusion">Conclusion
&lt;/h2>&lt;p>Those who enjoy watching historical costume dramas should be familiar that in every dynasty there was an office such as the &amp;ldquo;censor&amp;rdquo; or &amp;ldquo;remonstrance official&amp;rdquo;. As advisers who spoke truth to power, they were mostly unwelcome to emperors and ministers, yet the operation of the system could not do without this function of supervision and review.&lt;/p>
&lt;p>And testers are very much like the &amp;ldquo;censors&amp;rdquo; in the system of software development.&lt;/p>
&lt;p>Do not fear the &amp;ldquo;&lt;strong>fail&lt;/strong>&amp;rdquo; on a test report; that is precisely the meaning of the testing function&amp;rsquo;s existence.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825_hu_9cdb16702f1207a9.webp"
width="1024"
height="767"
srcset="https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825_hu_dd01b0253e8c5428.webp 480w, https://chengxiaqiucao.github.io/post/123-testing_not_valid/Pasted-20250825_hu_9cdb16702f1207a9.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="133"
data-flex-basis="320px"
>
&lt;/p></description></item><item><title>"Bug Count", a Bad Metric</title><link>https://chengxiaqiucao.github.io/en/post/120-bad_metric_bug/</link><pubDate>Fri, 15 Aug 2025 17:21:34 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/120-bad_metric_bug/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815-2.webp" alt="Featured image of post "Bug Count", a Bad Metric" />&lt;h2 id="preface">Preface
&lt;/h2>&lt;p>In many software companies, for a long time, &lt;code>Bug count&lt;/code> has been regarded as an intuitive metric for measuring quality and team performance.&lt;/p>
&lt;p>But in reality, using &lt;code>Bug count&lt;/code> as a performance metric, a seemingly simple and direct way of measuring, actually has fundamental flaws. It not only fails to reflect the real value of individuals and teams, but also gives rise to the &amp;ldquo;Cobra effect&amp;rdquo;, hindering the team from moving toward genuine quality goals.&lt;/p>
&lt;p>In this article, we will analyze in depth the drawbacks of using &lt;code>Bug count&lt;/code> as a performance metric, and explore more reasonable ways of measuring.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815-2_hu_12d9771b62f53dc6.webp"
width="1024"
height="443"
srcset="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815-2_hu_9308e74afab11a78.webp 480w, https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815-2_hu_12d9771b62f53dc6.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="231"
data-flex-basis="555px"
>
&lt;/p>
&lt;h2 id="fundamental-drawbacks-of-the-bug-count-metric">Fundamental Drawbacks of the &amp;ldquo;Bug Count&amp;rdquo; Metric
&lt;/h2>&lt;p>Taking &lt;strong>defect count&lt;/strong> as a single indicator of performance assessment essentially reduces the complex, multi-dimensional goal of &lt;strong>quality&lt;/strong> to a single, quantifiable number.&lt;/p>
&lt;p>Such simplification creates a fatal gap between actual measurement and expectation, thereby fundamentally violating the purpose of software engineering.&lt;/p>
&lt;h3 id="the-cobra-effect">The Cobra Effect
&lt;/h3>&lt;p>Any single, quantified data metric, once it becomes a performance measure, tends to trigger negative results contrary to its original design intent, giving rise to the &lt;strong>Cobra Effect&lt;/strong>&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815-1_hu_f82ea9df9adb8415.webp"
width="1024"
height="575"
srcset="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815-1_hu_1f642ef483d76df7.webp 480w, https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815-1_hu_f82ea9df9adb8415.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="177"
data-flex-basis="427px"
>
&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>The Cobra Effect&lt;/strong> originated in India during British rule. To control the cobra population, the government offered a bounty for killing them, but local residents began breeding cobras artificially to collect the bounty. When the government stopped the bounty, the released cobras caused an even worse infestation.&lt;/p>&lt;/blockquote>
&lt;p>In the software development process, obsessive metrics like &lt;code>Bug count&lt;/code> can likewise produce outcomes that backfire.&lt;/p>
&lt;p>&lt;strong>For the testing team&lt;/strong>, this way of measuring gives rise to the typical problem of &amp;ldquo;valuing quantity over quality&amp;rdquo;. To meet a &amp;ldquo;defect quota&amp;rdquo; or performance target, testers tend to waste precious time looking for minor issues that have low impact and low priority but are easy to find, just to &amp;ldquo;pad the numbers&amp;rdquo;. As a result, a great deal of development and business resources are wasted.&lt;/p>
&lt;p>Beyond that, when the goal focuses on quantity, testers tend to stop doing in-depth analysis of Bugs, that is, they stop pursuing high-value &lt;code>Bug reports&lt;/code> (see the previous article 【】). So this kind of metric design actually punishes those testers committed to providing high-value insights.&lt;/p>
&lt;p>&lt;strong>For the development team&lt;/strong>, if a developer&amp;rsquo;s performance is tied to the &amp;ldquo;number of bugs fixed&amp;rdquo;, they have more incentive to fix the &amp;ldquo;small and beautiful&amp;rdquo;, easy-to-solve bugs rather than tackle a high-value, complex, deep-seated fault. It may even lead to &amp;ldquo;producing and consuming one&amp;rsquo;s own&amp;rdquo;, where they actively create easy-to-fix defects just to meet the fix-count/fix-rate metric.&lt;/p>
&lt;p>So it is clear that the result ultimately driven by the metric runs counter to real value.&lt;/p>
&lt;h3 id="ignoring-the-essence-of-quality-goals">Ignoring the Essence of Quality Goals
&lt;/h3>&lt;p>In my previous article 【】 I analyzed in depth the real purpose of engaging in software testing. One important point is:&lt;/p>
&lt;blockquote>
&lt;p>Software testing is not for finding Bugs&lt;/p>&lt;/blockquote>
&lt;p>But this metric explicitly sets finding Bugs as the purpose of the testing work.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815_hu_d0b8fef02b09acad.webp"
width="1024"
height="1354"
srcset="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815_hu_4bb34638a71fc987.webp 480w, https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250815_hu_d0b8fef02b09acad.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="75"
data-flex-basis="181px"
>
&lt;/p>
&lt;p>The purpose of testing is to accurately present the quality status of the product. And the overall quality status is unknown; pursuing Bug count will inevitably make testers invest more energy in the superficial, easy-to-trigger parts that are not critical to the system, while neglecting the parts that require in-depth analysis and more comprehensive exploration.&lt;/p>
&lt;p>In other words, this metric actually encourages shallow testing but punishes deep testing.&lt;/p>
&lt;p>And under this orientation, &amp;ldquo;shift-left testing&amp;rdquo; actually becomes empty talk; the greater the contribution of shift-left, the fewer Bugs are found later. It even hinders improvements in team efficiency and knowledge sharing within the testing team.&lt;/p>
&lt;h3 id="creating-team-conflict-and-destroying-psychological-safety">Creating Team Conflict and Destroying Psychological Safety
&lt;/h3>&lt;p>Establishing this metric also creates an opposition of &amp;ldquo;Tester vs Developer&amp;rdquo;, thereby destroying the cornerstone of a high-performing team - psychological safety.&lt;/p>
&lt;p>Psychological safety means team members can freely express ideas, take risks, and admit mistakes without fear of negative consequences.&lt;/p>
&lt;p>But when testers are incentivized to report more Bugs while developers are expected to produce as few Bugs as possible, the inevitable result is developers questioning whether a Bug is just the tester &amp;ldquo;padding the numbers&amp;rdquo;, and testers believing developers are merely making excuses to reduce the Bug count.&lt;/p>
&lt;p>Such a metric creates a &amp;ldquo;culture of blame&amp;rdquo;. The trust relationship between the two teams naturally breaks down.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250220-2_hu_b28dfb177ff354a9.webp"
width="1024"
height="541"
srcset="https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250220-2_hu_67e9f792be63dae4.webp 480w, https://chengxiaqiucao.github.io/post/120-bad_metric_bug/Pasted-20250220-2_hu_b28dfb177ff354a9.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="189"
data-flex-basis="454px"
>
&lt;/p>
&lt;h2 id="building-value-oriented-quality-measurement">Building Value-Oriented Quality Measurement
&lt;/h2>&lt;p>Since &amp;ldquo;Bug count&amp;rdquo; is clearly unsuitable for performance measurement, and quality, as a black box, is indeed hard to measure fully accurately, here we can establish a value-oriented quality measurement system from the following aspects.&lt;/p>
&lt;h3 id="product-quality-dimension">Product Quality Dimension
&lt;/h3>&lt;p>First, for the product itself and delivery quality, consider the following metrics:&lt;/p>
&lt;h4 id="1-customer-and-user-experience-metrics">(1) Customer and User Experience Metrics
&lt;/h4>&lt;ul>
&lt;li>
&lt;p>&lt;strong>Customer-reported functional defects&lt;/strong>: Compared with Bugs found internally, problems reported by customers better reflect real quality impact. But priority should be given to high-severity issues (such as functional failure, data loss) rather than simple counting.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Customer Satisfaction (CSAT) and Net Promoter Score (NPS)&lt;/strong>: Directly obtain users&amp;rsquo; evaluation of software quality through regular surveys; this is the most direct quality feedback.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;h4 id="2-system-stability-and-performance-metrics">(2) System Stability and Performance Metrics
&lt;/h4>&lt;ul>
&lt;li>
&lt;p>&lt;strong>System availability (Uptime)&lt;/strong>: Measure normal uptime as a percentage, e.g. 99.9% availability means allowed downtime of no more than 43.2 minutes per month.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Performance metrics&lt;/strong>: Including page load time, API response time, transaction throughput, etc., directly reflecting the user experience.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Deployment success rate&lt;/strong>: Measures the reliability of the release process; a high success rate means a stable release process and fewer deployment-induced problems.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Online failure rate&lt;/strong>: Counts the number of failures occurring in the production environment, prioritizing high-severity failures that affect users.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;h4 id="3-problem-response-and-fix-efficiency">(3) Problem Response and Fix Efficiency
&lt;/h4>&lt;ul>
&lt;li>
&lt;p>&lt;strong>Average time from problem identification to fix release&lt;/strong>: Measures the team&amp;rsquo;s response speed to problems; the shorter the time, the higher the fix efficiency.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Bug fix success rate&lt;/strong>: Counts the proportion of fixes that do not introduce new problems, reflecting fix quality.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Proportion of support tickets that need no escalation to developers&lt;/strong>: Measures the support team&amp;rsquo;s ability to solve problems independently; a higher proportion means a more stable system and better documentation.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;h3 id="process-quality-dimension">Process Quality Dimension
&lt;/h3>&lt;p>Quality is not something the testing or development team can be responsible for alone; to improve quality, we must consider the whole process. For example:&lt;/p>
&lt;h4 id="1-code-and-process-quality">(1) Code and Process Quality
&lt;/h4>&lt;ul>
&lt;li>&lt;strong>Code review cycle time&lt;/strong>: The average time from code submission to completed review; the shorter the time, the higher the collaboration efficiency.&lt;/li>
&lt;li>&lt;strong>Test coverage trend&lt;/strong>: Focus on the growth trend of coverage rather than the absolute percentage, reflecting the continuous improvement of the testing system.&lt;/li>
&lt;li>&lt;strong>Technical debt cleanup ratio&lt;/strong>: Counts the proportion of planned technical debt resolved, reflecting the team&amp;rsquo;s emphasis on long-term quality.&lt;/li>
&lt;/ul>
&lt;h4 id="2-team-health">(2) Team Health
&lt;/h4>&lt;ul>
&lt;li>&lt;strong>Sprint goal success rate&lt;/strong>: Measures the team&amp;rsquo;s plan execution ability; a high success rate means reasonable goal setting and efficient team collaboration.&lt;/li>
&lt;li>&lt;strong>Team member satisfaction&lt;/strong>: Understand team morale and job satisfaction through regular anonymous surveys; high satisfaction is the foundation of a high-performing team.&lt;/li>
&lt;li>&lt;strong>Number of process improvement suggestions&lt;/strong>: Counts the number of process optimization suggestions raised by the team, reflecting the team&amp;rsquo;s awareness of continuous improvement.&lt;/li>
&lt;/ul>
&lt;h3 id="business-value-dimension">Business Value Dimension
&lt;/h3>&lt;p>Quality ultimately serves business value; considering this aspect:&lt;/p>
&lt;h4 id="1-feature-delivery-quality">(1) Feature Delivery Quality
&lt;/h4>&lt;ul>
&lt;li>
&lt;p>&lt;strong>Proportion of features requiring hotfix&lt;/strong>: Counts the proportion of new features that need emergency fixes after release; a lower proportion means higher development quality.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Number of support tickets after new feature release&lt;/strong>: Measures user acceptance of and problem feedback on new features; fewer tickets means higher feature quality.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;h4 id="2-long-term-impact">(2) Long-term Impact
&lt;/h4>&lt;ul>
&lt;li>
&lt;p>&lt;strong>Velocity trend&lt;/strong>: Observe the trend of the team&amp;rsquo;s development velocity; low-quality code causes velocity to gradually decline, while high-quality code maintains a stable velocity.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>System maintainability and scalability assessment&lt;/strong>: Through architecture reviews, code complexity analysis, and other means, regularly evaluate the long-term health of the system.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>Through this set of metrics, we should be able to measure the question &amp;ldquo;How good is the product quality actually?&amp;rdquo; fairly comprehensively.&lt;/p>
&lt;h2 id="conclusion">Conclusion
&lt;/h2>&lt;p>Through the analysis above, we have examined why &lt;code>Bug count&lt;/code> should not be used as a team performance metric; it can be said to do a hundred harms and no good.&lt;/p>
&lt;p>At the same time, we have given a multi-dimensional, value-oriented quality metric system that measures team quality more comprehensively and scientifically from the dimensions of product quality, process quality, and business value.&lt;/p>
&lt;p>Of course, there is no perfect metric system; every measurement has its limitations. The key is to maintain an open mind, regularly review and adjust the metrics, and avoid &amp;ldquo;metric dependency&amp;rdquo;. As the quality master W. Edwards Deming said, &lt;code>Quality is not determined by metrics, but by culture and systems&lt;/code>.&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>DeepSeek Prompt Frameworks Help Teams Improve the Status Quo and Boost Efficiency</title><link>https://chengxiaqiucao.github.io/en/post/069-%E4%BC%98%E5%8C%96ai%E6%8F%90%E7%A4%BA%E6%A1%86%E6%9E%B6%E5%AE%9E%E7%8E%B0%E5%9B%A2%E9%98%9F%E6%8F%90%E5%8D%87/</link><pubDate>Wed, 19 Mar 2025 22:44:42 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/069-%E4%BC%98%E5%8C%96ai%E6%8F%90%E7%A4%BA%E6%A1%86%E6%9E%B6%E5%AE%9E%E7%8E%B0%E5%9B%A2%E9%98%9F%E6%8F%90%E5%8D%87/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/069-%E4%BC%98%E5%8C%96ai%E6%8F%90%E7%A4%BA%E6%A1%86%E6%9E%B6%E5%AE%9E%E7%8E%B0%E5%9B%A2%E9%98%9F%E6%8F%90%E5%8D%87/%E6%8F%90%E7%A4%BA%E8%AF%8D%E6%A1%86%E6%9E%B6.webp" alt="Featured image of post DeepSeek Prompt Frameworks Help Teams Improve the Status Quo and Boost Efficiency" />&lt;p>With the rapid development of AI technology, from ChatGPT to the explosion of DeepSeek, AI can now genuinely play a role in assisting our daily work.&lt;/p>
&lt;p>Beyond specific areas such as assisted programming and copywriting, we can also make full use of AI&amp;rsquo;s powerful logical capabilities and vast foundational data to help us propose practical and feasible improvement plans for some of the difficulties we encounter at work.&lt;/p>
&lt;p>But for AI to give us actionable solutions, the design of the prompt framework and the contextual information provided to AI are extremely critical. A well-designed prompt framework can help us quickly obtain highly valuable references.&lt;/p>
&lt;h2 id="a-case-of-the-predicament-we-face">A Case of the Predicament We Face
&lt;/h2>&lt;p>Here we use a fairly common case of an agile team&amp;rsquo;s quality predicament to illustrate:&lt;/p>
&lt;blockquote>
&lt;p>As a test engineer responsible for quality assurance in an agile team running the Scrum framework, the team also includes an SM, a PO, two Android developers (among whom Xiao Li is responsible for the overall system design of the App), one back-end developer, and one part-time visual designer. The team&amp;rsquo;s product is a companion Android App for an IoT smart bracelet product. However, due to issues such as coordination with the hardware team, frequently changing requirements, untimely visual design, delayed test submissions, and a backlog of bugs, product quality is not optimistic. The App has now gone through multiple iterations, and the planned launch date is drawing ever closer. How can we propose an improvement plan for the current quality predicament?&lt;/p>&lt;/blockquote>
&lt;h3 id="designing-the-prompt-framework">Designing the Prompt Framework
&lt;/h3>&lt;p>For AI to help us produce a feasible improvement plan, we first need to design the prompt framework reasonably, so that the final plan better fits the team&amp;rsquo;s current situation and is actionable.&lt;/p>
&lt;p>The key points of the prompt framework design are then:&lt;/p>
&lt;ul>
&lt;li>A given role, so that AI determines from what perspective to propose the improvement plan&lt;/li>
&lt;li>The current status quo, that is, sufficient background information and context&lt;/li>
&lt;li>What AI should analyze in detail, or what its task should be&lt;/li>
&lt;li>The specific output expected from AI, including format requirements and the elements to be included&lt;/li>
&lt;li>Some relevant constraints, which have an important impact on whether the plan is feasible&lt;/li>
&lt;/ul>
&lt;p>Now, for the predicament above, I want AI to help me provide an overall quality improvement plan for the team that can be discussed at the retrospective meeting. Based on the above thinking, by inputting the prompt framework into DeepSeek, we get the following output:&lt;/p>
&lt;h3 id="quality-improvement-plan-for-the-iteration-retrospective">Quality Improvement Plan (For the Iteration Retrospective)
&lt;/h3>&lt;hr>
&lt;h4 id="1-overall-quality-goals">&lt;strong>1. Overall Quality Goals&lt;/strong>
&lt;/h4>&lt;p>&lt;strong>&amp;ldquo;Within 2 iterations, raise automated test coverage to 40%, shorten defect-fix response time by 50%, compress regression testing time by 30%, and establish a quality defense line linking requirement changes with testing&amp;rdquo;&lt;/strong>&lt;/p>
&lt;hr>
&lt;h4 id="2-specific-improvement-initiatives">&lt;strong>2. Specific Improvement Initiatives&lt;/strong>
&lt;/h4>&lt;table>
&lt;thead>
&lt;tr>
&lt;th>Initiative&lt;/th>
&lt;th>Owner&lt;/th>
&lt;th>Execution Plan&lt;/th>
&lt;th>Evaluation Method&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>&lt;strong>Requirement Freeze Mechanism&lt;/strong>&lt;br>- Lock core functional requirements 3 days before each iteration&lt;br>- Hardware integration requirements are jointly reviewed by the PO and the hardware team to form interface documents&lt;/td>
&lt;td>PO, hardware team lead&lt;/td>
&lt;td>Sign the requirements baseline document at the iteration planning meeting&lt;br>Share hardware interface documents via Confluence&lt;/td>
&lt;td>Reduce requirement changes by 50%&lt;br>Interface document version change records are traceable&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Automated Test Case Tiering Strategy&lt;/strong>&lt;br>- L0 (core business flows): mandatory full automation&lt;br>- L1 (high-frequency usage scenarios): prioritized for automation&lt;br>- L2 (edge scenarios): manual verification&lt;/td>
&lt;td>Test Engineer&lt;br>(Lead)&lt;br>Android Developer&lt;br>(Support)&lt;/td>
&lt;td>Use Allure to label case tiers&lt;br>Daily builds prioritize running L0 cases&lt;/td>
&lt;td>100% pass rate of L0 cases as the test-submission exit criterion&lt;br>Reduce automation execution time by 40%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Developer Self-Testing Responsibility&lt;/strong>&lt;br>- Code submitted by developers must include unit tests (coverage ≥60%)&lt;br>- API tests are maintained by back-end engineers in Swagger&lt;/td>
&lt;td>Android Developer&lt;br>Back-end Engineer&lt;/td>
&lt;td>Include unit tests as a code review checklist item&lt;br>Link Postman API cases with the code repository&lt;/td>
&lt;td>Raise the smoke-test pass rate of submitted builds to 80%&lt;br>Reduce the API defect rate by 30%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Hardware Compatibility Mock Service&lt;/strong>&lt;br>- Develop a simulator based on the hardware protocol&lt;br>- Decouple automated testing from real devices&lt;/td>
&lt;td>Test Engineer&lt;br>(Lead)&lt;br>Hardware team provides protocol documents&lt;/td>
&lt;td>Develop a Bluetooth protocol simulator using Python&lt;br>Automatically start the Mock service during Jenkins builds&lt;/td>
&lt;td>Reduce test blockages caused by hardware dependencies to zero&lt;br>Raise automation stability to 95%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>&lt;strong>Defect Severity Management&lt;/strong>&lt;br>- P0 defects: respond within 2 hours&lt;br>- P1 defects: must be fixed in the current iteration&lt;br>- Residual defects require the PO to sign off on the risk&lt;/td>
&lt;td>Test Engineer&lt;br>(Classification)&lt;br>Developer&lt;br>(Fix)&lt;/td>
&lt;td>Configure automated defect workflow rules in Jira&lt;br>Sync the progress of the top 3 defects at the daily stand-up&lt;/td>
&lt;td>Shorten the average defect-fix cycle to 8 hours&lt;br>Reduce the number of backlogged defects by 60%&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;hr>
&lt;h4 id="3-risks-and-responses">&lt;strong>3. Risks and Responses&lt;/strong>
&lt;/h4>&lt;table>
&lt;thead>
&lt;tr>
&lt;th>Risk&lt;/th>
&lt;th>Response&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>Developers resist unit testing&lt;/td>
&lt;td>- Xiao Li (the system designer) demonstrates writing unit tests&lt;br>- Incorporate test coverage into the DoD completion criteria&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>The hardware protocol changes frequently&lt;/td>
&lt;td>- Require the hardware team to notify of protocol changes 3 days in advance&lt;br>- Design a version compatibility mechanism for the Mock service&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>UE design delays affect UI testing&lt;/td>
&lt;td>- Agree with the UE designer: deliver UI element ID specifications together with the visual drafts&lt;br>- Use a screenshot comparison tool with a 10% pixel-difference tolerance&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;hr>
&lt;h4 id="4-external-support-requirements">&lt;strong>4. External Support Requirements&lt;/strong>
&lt;/h4>&lt;table>
&lt;thead>
&lt;tr>
&lt;th>Type&lt;/th>
&lt;th>Specific Requirements&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>Tools&lt;/td>
&lt;td>- Apply for a BrowserStack mobile cloud testing platform license&lt;br>- Purchase an Xray test case management plugin license&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>People&lt;/td>
&lt;td>- The hardware team designates a protocol liaison&lt;br>- A DevOps engineer optimizes the CI/CD pipeline&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>Training&lt;/td>
&lt;td>- Invite a unit testing expert to run a TDD workshop&lt;br>- Internal training on advanced Appium usage&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;hr>
&lt;h4 id="5-effect-evaluation-milestones">&lt;strong>5. Effect Evaluation Milestones&lt;/strong>
&lt;/h4>&lt;table>
&lt;thead>
&lt;tr>
&lt;th>Milestone&lt;/th>
&lt;th>Verification Criteria&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td>Mid-iteration 5&lt;/td>
&lt;td>- L0 automated cases cover all core business flows&lt;br>- Unit test coverage ≥40%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>End of iteration 5&lt;/td>
&lt;td>- Automation coverage ≥25%&lt;br>- Regression testing time ≤8 hours per run&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td>End of iteration 6&lt;/td>
&lt;td>- Automation coverage ≥40%&lt;br>- Zero fatal defects in the production environment&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;hr>
&lt;p>&lt;strong>Notes on Key Execution Points:&lt;/strong>&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Daily Quality Dashboard&lt;/strong>: Hang the automation execution rate / defect trend chart in the team war room&lt;/li>
&lt;li>&lt;strong>Quality Gate Mechanism&lt;/strong>: Code merge requests must pass L0 cases plus SonarQube checks&lt;/li>
&lt;li>&lt;strong>Shift-Left Testing Practice&lt;/strong>: Test engineers produce a test-point matrix as soon as they participate in requirement reviews&lt;/li>
&lt;/ol>
&lt;p>This plan requires the whole team to sign a quality commitment letter. It is recommended that, at the iteration retrospective, the team use the &amp;ldquo;5 Whys analysis&amp;rdquo; to reach a consensus on improvement regarding the current quality issues.&lt;/p>
&lt;p>As we can see, we have obtained an improvement plan that is highly targeted and quite feasible. Based on the team&amp;rsquo;s current situation, we can actually put it into implementation after some fine-tuning.&lt;/p>
&lt;p>So making good use of AI prompt frameworks can not only help us get assistance on specific tasks, but also provide tremendous support for overall improvement initiatives of this kind.&lt;/p>
&lt;p>Reply with &amp;ldquo;prompt framework&amp;rdquo; to get the complete prompt example shown above. Regarding more practical applications of AI at work, everyone is also welcome to leave comments or join the group to discuss!&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/qrcode_for_gh_e12c318badb4_258%20%281%29.jpg"
loading="lazy"
>
&lt;/p></description></item><item><title>Some Pitfalls in Software Testing - Things We Can Do but Should Not Do</title><link>https://chengxiaqiucao.github.io/en/post/067-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E4%B8%AD%E5%8F%AF%E5%81%9A%E4%BD%86%E4%B8%8D%E5%BA%94%E5%81%9A%E7%9A%84%E4%B8%80%E4%BA%9B%E9%99%B7%E9%98%B1/</link><pubDate>Tue, 18 Mar 2025 16:49:04 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/067-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E4%B8%AD%E5%8F%AF%E5%81%9A%E4%BD%86%E4%B8%8D%E5%BA%94%E5%81%9A%E7%9A%84%E4%B8%80%E4%BA%9B%E9%99%B7%E9%98%B1/</guid><description>&lt;h2 id="8-kinds-of-work-in-software-testing-that-">8 Kinds of Work in Software Testing That &lt;strong>&amp;ldquo;We Can Do, but Should Not Do&amp;rdquo;&lt;/strong>
&lt;/h2>&lt;p>In software testing, we often face a problem - many tasks are indeed things we can accomplish, and doing them may seem perfectly natural, yet in many cases these efforts yield very little. These range from over-automation to frequently running unnecessary regression tests, to name a few.&lt;/p>
&lt;p>As technology evolves, the tools available to testers let us accomplish far more, but that does not mean every choice is a wise one. Some tasks, when done blindly, tend to undermine the things that truly matter - output, efficiency, maintainability, and so on.&lt;/p>
&lt;p>This article lists eight pieces of work in testing that &amp;ldquo;we can do, but should not do&amp;rdquo;. Sometimes, taking a step back is the smarter choice.&lt;/p>
&lt;h3 id="1-automating-all-tests">1. Automating All Tests
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> Modern test automation tools let us automate almost any test case - from every click in the user interface to every API call - all of which can technically be driven through automation.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> Just because test automation is feasible does not mean it is the best choice. For example:&lt;/p>
&lt;blockquote>
&lt;p>A product&amp;rsquo;s user interface is highly dynamic, with designers adjusting it every week. If you choose to automate every test, the relevant automated tests risk breaking after each UI change.&lt;/p>&lt;/blockquote>
&lt;p>In this case, &lt;strong>manual testing may be more effective&lt;/strong>.&lt;/p>
&lt;h3 id="2-using-overly-complex-locators-in-automation-scripts">2. Using Overly Complex Locators in Automation Scripts
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> In automation tools such as Selenium and Playwright, XPath and CSS selectors let us pinpoint even the deepest elements on a page.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> Overly complex locators tend to make tests fragile. For example:&lt;/p>
&lt;blockquote>
&lt;p>Using a complex XPath to locate a menu often causes multiple tests to fail once the development team refactors the HTML structure, forcing the team to spend a great deal of time on fixes.&lt;/p>&lt;/blockquote>
&lt;p>At this point, other approaches may be more effective for the stability of automated cases, such as &lt;strong>agreeing with the development team to add a &lt;code>test-id&lt;/code> attribute to elements&lt;/strong>.&lt;/p>
&lt;h3 id="3-running-the-full-regression-suite-on-every-commit">3. Running the Full Regression Suite on Every Commit
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> In modern CI/CD pipelines, every code commit can easily trigger a full regression run.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> In practice, this is often excessive. Imagine a small code fix triggering the entire regression suite, a process that may take several hours or even longer.&lt;/p>
&lt;p>For teams that have not raised automation coverage to a certain level, running a full regression after each commit is an even worse nightmare. The better approach is still to stay on top of what changed and implement &lt;strong>precise testing&lt;/strong> based on the changes and their impact.&lt;/p>
&lt;h3 id="4-over-mocking-in-api-testing">4. Over-Mocking in API Testing
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> Mocking API responses can greatly speed up testing and remove dependencies on external services.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> Over-mocking, however, cuts us off from the real environment. A large number of Mock APIs can indeed improve debugging and verification efficiency, but they depart from what genuine testing requires. &lt;strong>Testing in real scenarios is indispensable&lt;/strong>, just as we cannot anticipate every exception.&lt;/p>
&lt;h3 id="5-writing-extremely-detailed-bug-reports-for-trivial-issues">5. Writing Extremely Detailed Bug Reports for Trivial Issues
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> With the help of assistive testing tools, we can catch many small defects in the UI layer, in prompt messages, and the like, and we can write extremely thorough bug reports following case specifications.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> Not every minor issue deserves an exhaustive, blow-by-blow report. The purpose of finding a bug is ultimately to fix the bug, not the bug itself, and the value of bugs also varies in importance. I once analyzed what makes a good bug report in 【】 - the value of a bug report lies in being a channel for communicating with developers; the boilerplate text of the report itself has no value.&lt;/p>
&lt;h3 id="6-using-ai-to-generate-test-cases-without-human-supervision">6. Using AI to Generate Test Cases Without Human Supervision
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> Advances in AI have actually made it possible to use AI tools to rapidly generate large numbers of test cases from requirements documents, covering a wide range of scenarios.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> Today&amp;rsquo;s AI, however, especially for a specific business domain, lacks human contextual understanding and the combined information gathered through various internal communications, which can lead to redundant cases or to missing critical test cases.&lt;/p>
&lt;h3 id="7-using-too-many-assertions-in-a-test">7. Using Too Many Assertions in a Test
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> Combining automation tools with AI, we can indeed verify a large number of fields, properties, and UI elements within a single test.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> Too many assertions, however, only make a test huge and complex and hard to debug. When some assertions fail, it often takes a great deal of effort to track down the cause.&lt;/p>
&lt;h3 id="8-executing-tests-on-every-possible-device-and-browser-combination">8. Executing Tests on Every Possible Device and Browser Combination
&lt;/h3>&lt;p>&lt;strong>You can:&lt;/strong> For compatibility testing, modern cross-browser and cross-device testing tools let us run tests across many operating systems and devices.&lt;/p>
&lt;p>&lt;strong>But you shouldn&amp;rsquo;t:&lt;/strong> Testing every possible combination is neither necessary nor practical. The focus should be on covering the key scenarios that users actually use. Moreover, developments in engineering such as responsive design have greatly reduced the risk of compatibility issues.&lt;/p>
&lt;h3 id="conclusion">Conclusion
&lt;/h3>&lt;p>In software testing, &amp;ldquo;being able to do it&amp;rdquo; does not always mean it is the best choice. We need to find a balance between technical capability and practical feasibility. By avoiding these &amp;ldquo;because we can&amp;rdquo; pitfalls and building a lean, efficient, and genuinely valuable test suite, we contribute far more meaningfully to product quality assurance.&lt;/p>
&lt;p>Welcome to follow QiuCao for a steady stream of more hands-on technical content on software quality!&lt;/p></description></item><item><title>How to Complete Testing Quickly</title><link>https://chengxiaqiucao.github.io/en/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/</link><pubDate>Wed, 12 Feb 2025 15:31:20 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212.webp" alt="Featured image of post How to Complete Testing Quickly" />&lt;blockquote>
&lt;p>A reader asked how to complete testing quickly when the team has no dedicated testers.&lt;/p>&lt;/blockquote>
&lt;p>Let me start with the conclusion: there is no standard answer here!&lt;/p>
&lt;p>Having no testing role only means there is no one specifically responsible for this function; but the work of testing itself has not disappeared.&lt;/p>
&lt;p>&amp;ldquo;Completing testing quickly&amp;rdquo; is really better put as &amp;ldquo;quickly building quality confidence.&amp;rdquo;&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212_hu_bb249cab9e0ff57b.webp"
width="1024"
height="1024"
srcset="https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212_hu_d85629f65732b67.webp 480w, https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212_hu_bb249cab9e0ff57b.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="100"
data-flex-basis="240px"
>
&lt;/p>
&lt;p>Because testing is endless, there is no such thing as absolutely &amp;ldquo;finishing testing.&amp;rdquo; Based on past experience or a general consensus, once everyone basically agrees the product is probably fine, testing counts as done.&lt;/p>
&lt;p>So if what we want is to quickly build this quality confidence — or to quickly reach a consensus with stakeholders that quality is OK — what factors should we consider along these lines?&lt;/p>
&lt;h3 id="scope-to-be-tested">Scope to Be Tested
&lt;/h3>&lt;p>One way to finish testing quickly is to have a small test scope — for example, a tiny change with no related affected modules, so a quick check is enough. The logic is the same as committing development code promptly and integrating frequently: don&amp;rsquo;t accumulate changes, so you save the time of tracing back through a pile of changes when something goes wrong.&lt;/p>
&lt;p>Do thorough self-testing during development and integrate and test in time; don&amp;rsquo;t accumulate changes.&lt;/p>
&lt;h3 id="existing-quality">Existing Quality
&lt;/h3>&lt;p>Another aspect is whether you have confidence in the product&amp;rsquo;s existing quality. Development is incremental, so was the quality of the existing baseline up to standard? Are the relationships and impacts between the new and existing parts all known? Product quality is holistic; historical features and their effects also bear on current quality confidence. So whether the relationship between new and existing parts is clear, and whether the existing baseline itself is sound, are also critical.&lt;/p>
&lt;h3 id="potential-problems">Potential Problems
&lt;/h3>&lt;p>Then again, testing is black-box, so you can&amp;rsquo;t clearly know how much danger lies beneath the iceberg. But quality confidence actually has no direct relationship with potential problems; it mainly relates to known problems and tested scope — the fewer known problems and the larger the tested scope, the stronger the confidence. The logic behind it: more known problems often mean more potential ones; spotting one cockroach may mean a whole nest of them. So the emphasis is still on the quality of what&amp;rsquo;s handed over for testing! If self-testing isn&amp;rsquo;t thorough, don&amp;rsquo;t move on to integration testing yet — every developer should first sweep their own little patch clean.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212-1_hu_3436d1767471be2c.webp"
width="1024"
height="1024"
srcset="https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212-1_hu_a7d533b964634c5.webp 480w, https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212-1_hu_3436d1767471be2c.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="100"
data-flex-basis="240px"
>
&lt;/p>
&lt;h3 id="risk-of-problems-surfacing">Risk of Problems Surfacing
&lt;/h3>&lt;p>Finally, there is one more firewall: the risk of problems surfacing. A problem surfaces — boom! But the impact of that &amp;ldquo;boom&amp;rdquo; varies: is it just a spark that dies out, or does it blow a hole, or even bring down the whole building? Beyond the size of the problem itself, different products have different tolerance for problems. Setting off a firecracker in a building slated for demolition just means it gets demolished a bit early — tolerance is high, so confidence is high!&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212-2_hu_32d6656044eb503c.webp"
width="1024"
height="576"
srcset="https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212-2_hu_e96a6ad0c2c0168d.webp 480w, https://chengxiaqiucao.github.io/post/054-%E5%A6%82%E4%BD%95%E5%BF%AB%E9%80%9F%E5%AE%8C%E6%88%90%E6%B5%8B%E8%AF%95/Pasted-20250212-2_hu_32d6656044eb503c.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="177"
data-flex-basis="426px"
>
&lt;/p>
&lt;h2 id="summary">Summary
&lt;/h2>&lt;p>Taking all of the above together, completing testing quickly ultimately comes down to whether you can build delivery confidence as soon as possible, which depends on individual capability, product characteristics, and the development process. It&amp;rsquo;s really a matter of mindset.&lt;/p>
&lt;p>Lastly, it has to be said: nothing can defy its inherent laws. A system that runs stably, is robust and hard-wearing can only be achieved through all kinds of running-in and tempered by all kinds of internal and external problems.&lt;/p>
&lt;p>The &amp;ldquo;fast delivery&amp;rdquo; and &amp;ldquo;winning it all in one battle&amp;rdquo; you imagine — there is no such thing as peaceful times; it&amp;rsquo;s just that someone else is carrying the weight for you. And the one carrying it might be the developers in the early stage, the testers, or the operations staff — or, in the end, the users who bear it all!&lt;/p></description></item><item><title>The 5 Whys Root Cause Analysis Method You Should Know</title><link>https://chengxiaqiucao.github.io/en/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/</link><pubDate>Sat, 05 Oct 2024 00:00:00 +0000</pubDate><guid>https://chengxiaqiucao.github.io/en/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/5why.webp" alt="Featured image of post The 5 Whys Root Cause Analysis Method You Should Know" />&lt;p>In the field of quality management, an important process for improving quality is discovering problems and solving them. Within this, in the practice of solving problems, a key step is Root Cause Analysis (RCA). There are many RCA methods; commonly used ones include the Fishbone Diagram, the Affinity Diagram, and FMEA (Failure mode and effects analysis), among others.&lt;/p>
&lt;p>However, the easiest to apply and the most widely used is probably the 5 Whys root cause analysis method&lt;/p>
&lt;h2 id="the-origin-of-the-5-whys">The Origin of the 5 Whys
&lt;/h2>&lt;p>The &lt;strong>5 Whys&lt;/strong> method originated at Toyota and was proposed by &lt;strong>Akio Toyoda&lt;/strong>, the father of Toyota. But its introduction into the mainstream was thanks to &lt;strong>Taiichi Ohno&lt;/strong>, the head of the Toyota Production System.&lt;/p>
&lt;p>Toyota&amp;rsquo;s website has the following passage describing Taiichi Ohno&amp;rsquo;s advocacy of this method:&lt;/p>
&lt;blockquote>
&lt;p>Whenever a problem cropped up, Taiichi Ohno encouraged his staff to explore problems first-hand until the root causes were found. “Observe the production floor without preconceptions,” he would advise. “Ask ‘why’ five times about every matter.”&lt;/p>&lt;/blockquote>
&lt;p>The 5 Whys method is based on the following basic understanding:&lt;/p>
&lt;blockquote>
&lt;p>&amp;ldquo;Behind every problem there is a cause, but superficial analysis can only describe the symptoms.&amp;rdquo; To find the root cause behind a problem, continuous investigation is needed; only by obtaining the root cause can targeted, lasting solutions be adopted so that the problem does not recur.&lt;/p>&lt;/blockquote>
&lt;p>So the 5 Whys is actually about this: when we encounter a problem, we should not look only at the superficial causes that led to it, but should embrace the spirit of &amp;ldquo;getting to the bottom of the matter&amp;rdquo; and dig out its root cause. Only by solving the root cause that gives rise to the problem can we possibly avoid its repeated recurrence.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007_hu_83c5bf6cc8544e67.webp"
width="1024"
height="554"
srcset="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007_hu_408f310afb8edb6c.webp 480w, https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007_hu_83c5bf6cc8544e67.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="184"
data-flex-basis="443px"
>
&lt;/p>
&lt;p>To take an example from the software industry: during customer acceptance, a fairly serious functional bug was found that affected the final delivery of the product. At this point, the 5 Whys method is used to analyze the root cause:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>&lt;strong>Why did the customer encounter this problem?&lt;/strong> According to the technical lead, the testing team had not reported any such issue to the development team&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Why was the testing team unable to find the problem?&lt;/strong> The testing team only performed smoke testing and did not carry out complete regression verification of the functionality&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Why did the testing team only perform smoke testing&lt;/strong>? Because they did not have enough time to perform thorough regression verification of the entire application&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Why was there not enough time for thorough regression&lt;/strong>? Because the version submitted by development for testing was only one day ahead of the final delivery to the customer for acceptance, while thorough functional testing requires at least 3 days.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Why did development submit the build for testing only one day before delivery&lt;/strong>? Because the implementation of one key feature turned out to be more complex than expected and took more time.&lt;/p>
&lt;/li>
&lt;/ol>
&lt;p>Analyzing up to this point, two root causes are actually discovered:&lt;/p>
&lt;ul>
&lt;li>Team members made a serious misestimation of the workload, and development time was underestimated&lt;/li>
&lt;li>Problems in project management: the build was submitted for testing much later than the testing estimate, sacrificing quality by delivering to the customer without regression. Release-exit control was insufficient.&lt;/li>
&lt;/ul>
&lt;p>Therefore, based on the causes identified, improvements are needed in two areas to prevent similar situations from recurring.&lt;/p>
&lt;ol>
&lt;li>Improve the development team&amp;rsquo;s accuracy in estimating feature implementation, including training, requirements breakdown, and understanding requirements as early as possible.&lt;/li>
&lt;li>Improve project management by strengthening test entry/exit control and risk prevention. If the build is submitted late, the delivery time should be postponed accordingly; if a product is released without completing regression, at minimum an exception-release review process must be completed.&lt;/li>
&lt;/ol>
&lt;h2 id="implementation-steps-of-the-5-whys">Implementation Steps of the 5 Whys
&lt;/h2>&lt;p>Although the 5 Whys method is very simple, its implementation still needs to follow a certain process of steps:&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-3_hu_54d6781991275b33.webp"
width="1024"
height="182"
srcset="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-3_hu_e79cba6762181cbf.webp 480w, https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-3_hu_54d6781991275b33.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="561"
data-flex-basis="1347px"
>
&lt;/p>
&lt;ol>
&lt;li>
&lt;p>First, of course, the key members related to the problem need to jointly analyze it. In this step, all relevant roles in the team connected to the problem should be able to participate. Otherwise, the absence of key personnel may cause the analysis to be unable to proceed.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>After determining the team members who will participate, it is also necessary to ensure that everyone is fairly clear about the problem: what needs to be analyzed? What background information is there? The team should reach a consensus on the understanding of the problem, rather than entering the Why discussion with different interpretations&lt;/p>
&lt;/li>
&lt;li>
&lt;p>During the specific analysis meeting, the facilitator should, through appropriate questioning, gradually help the team unearth the real causes&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Of course, the ultimate purpose of analyzing a problem is to solve it, so we also need to discuss corresponding corrective measures for the root cause obtained, in order to prevent similar problems from happening again.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Finally, how effective the implementation of the corrective measures is also needs to be tracked with corresponding actions and time nodes, so as to verify and confirm the effectiveness of the root cause analysis.&lt;/p>
&lt;/li>
&lt;/ol>
&lt;p>Only through such a process is it a complete root cause analysis implementation based on the 5 Whys method.&lt;/p>
&lt;h2 id="considerations-when-implementing-the-5-whys">Considerations When Implementing the 5 Whys
&lt;/h2>&lt;p>Although the 5 Whys method is simple, in practice it is actually not easy to do well. Here are some key points to note:&lt;/p>
&lt;h3 id="a-team-activity">A Team Activity
&lt;/h3>&lt;p>The 5 Whys analysis is a team activity that requires the active participation of people related to the problem. Only when the key roles along the problem analysis path can give effective answers can the validity of the analysis chain be guaranteed&lt;/p>
&lt;h3 id="not-an-efficient-method">Not an Efficient Method
&lt;/h3>&lt;p>Although this method is simple to understand, because it is a team activity and is closely tied to whether the various background information about the problem is sufficient, activities including information collection, gathering personnel, and brainstorming in meetings all require an investment of time. It is not an activity that reaches conclusions efficiently or quickly; sometimes it even requires multiple meeting discussions.&lt;/p>
&lt;h3 id="the-facilitators-experience">The Facilitator&amp;rsquo;s Experience
&lt;/h3>&lt;p>Whether the 5 Whys method succeeds depends critically on the role of the meeting facilitator. This role should have a full understanding of the 5 Whys method and be fairly familiar with the problem-related domain, able to guide the team to dig for root causes in the right direction and avoid excessive divergence&lt;/p>
&lt;h3 id="focus-on-the-issue-not-the-person-avoid-shifting-blame">Focus on the Issue, Not the Person; Avoid Shifting Blame
&lt;/h3>&lt;p>Root cause analysis is not about assigning blame; that is, the focus of the meeting is to discover points for future improvement, not to define responsibility for the current problem, so as to avoid turning the analysis meeting into a blame-shifting or finger-pointing session&lt;/p>
&lt;h3 id="focus-on-controllable-factors">Focus on Controllable Factors
&lt;/h3>&lt;p>The root causes obtained from root cause analysis should be controllable factors on which action can be taken, rather than finding force majeure factors that simply cannot be corrected. For example, if there is a shortage of staff, the root cause is that the company is not performing well, and the company&amp;rsquo;s poor performance is due to an economic downturn.. The conclusion would then fizzle out with nothing being done.&lt;/p>
&lt;p>All in all, the 5 Whys analysis method is a simple and practical root cause analysis method, but it is not an efficient one, and its effectiveness is closely related to the concerted effort of team members and the way it is implemented. Only by understanding its internal logic and implementing it selectively according to the team&amp;rsquo;s actual situation can it truly have the effect it should.&lt;/p>
&lt;h2 id="analysis-templates">Analysis Templates
&lt;/h2>&lt;p>Two common analysis templates are attached below for your reference&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-1_hu_562a91aa259b54e.webp"
width="1024"
height="628"
srcset="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-1_hu_c2702d3a55e65e01.webp 480w, https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-1_hu_562a91aa259b54e.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="162"
data-flex-basis="391px"
>
&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-2_hu_c1bd76f09bb2689a.webp"
width="1024"
height="634"
srcset="https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-2_hu_59330e6a7c9c33be.webp 480w, https://chengxiaqiucao.github.io/post/027-%E8%B4%A8%E9%87%8F%E7%AE%A1%E7%90%86%E4%B8%8D%E5%8F%AF%E4%B8%8D%E7%9F%A5%E7%9A%845why%E6%A0%B9%E5%9B%A0%E5%88%86%E6%9E%90%E6%B3%95/Pasted-20241007-2_hu_c1bd76f09bb2689a.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="161"
data-flex-basis="387px"
>
&lt;/p>
&lt;hr></description></item></channel></rss>