<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Career Development on Testing Observation</title><link>https://chengxiaqiucao.github.io/en/tags/career-development/</link><description>Recent content in Career Development on Testing Observation</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>|by Daniel Wei</copyright><lastBuildDate>Thu, 04 Sep 2025 22:28:02 +0800</lastBuildDate><atom:link href="https://chengxiaqiucao.github.io/en/tags/career-development/index.xml" rel="self" type="application/rss+xml"/><item><title>What Can a Test Engineer Do When There Is "Nothing to Test"?</title><link>https://chengxiaqiucao.github.io/en/post/125-no_test_time/</link><pubDate>Thu, 04 Sep 2025 22:28:02 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/125-no_test_time/</guid><description>&lt;h1 id="what-can-a-test-engineer-do-when-there-is-nothing-to-test">What Can a Test Engineer Do When There Is &amp;ldquo;Nothing to Test&amp;rdquo;?
&lt;/h1>&lt;blockquote>
&lt;p>As a software test engineer, you have probably experienced this: the developers are still coding, there are no tasks waiting to be tested on the board, no upcoming release, and no regression testing requirements&amp;hellip;
Especially in the early development stage of a waterfall team, or the early stage of an iteration in agile mode.
&amp;ldquo;Nothing to test&amp;rdquo; - relaxed, yet a bit idle, with a vague anxiety of wasting your life&lt;/p>&lt;/blockquote>
&lt;p>But in fact, &lt;strong>there is always something to test. Always.&lt;/strong>&lt;/p>
&lt;p>If there are no features to test, there are still many ways we can contribute to product quality: improve the testing process, or improve our own skills as QA professionals.&lt;/p>
&lt;p>In fact, these &amp;ldquo;relaxed&amp;rdquo; moments can be seen as opportunities for yourself and the project.&lt;/p>
&lt;h2 id="explore-the-product-in-depth">Explore the Product in Depth
&lt;/h2>&lt;p>Use this time to explore the application like a curious user, doing some exploratory testing. Because you have time, you can be more creative and think of scenarios or edge cases you have not tried before. You can also pick parts of the application that are rarely tested and use this time to explore them, checking whether everything there works properly.&lt;/p>
&lt;p>You will often find unexpected behaviors that are not exposed in normal testing scenarios. Report everything you find and notify the team. In addition, you can record the scenarios you tried, and later add some of them to the list of all test cases for use in the next round of testing.&lt;/p>
&lt;h2 id="clean-up-and-improve-test-cases">Clean Up and Improve Test Cases
&lt;/h2>&lt;p>Quiet time is a good time to review test cases and check their quality. You can review them:&lt;/p>
&lt;ul>
&lt;li>To see whether they are up to date?&lt;/li>
&lt;li>Whether they are clear and easy to understand. Are there cases that need updating?&lt;/li>
&lt;li>Are there steps that can be simplified?&lt;/li>
&lt;li>Are there scenarios you know about but have not yet documented?&lt;/li>
&lt;/ul>
&lt;p>This will help when using them in the future. You will be more confident that the test cases are up to date, improved, and provide good test coverage.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/125-no_test_time/kanban_hu_db7cce2d3788d84e.webp"
width="1024"
height="598"
srcset="https://chengxiaqiucao.github.io/post/125-no_test_time/kanban_hu_822e9c734857b46d.webp 480w, https://chengxiaqiucao.github.io/post/125-no_test_time/kanban_hu_db7cce2d3788d84e.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="171"
data-flex-basis="410px"
>
&lt;/p>
&lt;h2 id="improve-test-documentation">Improve Test Documentation
&lt;/h2>&lt;p>Although it may not be very interesting, it is useful to use this time to review and update any test documentation you have.&lt;/p>
&lt;p>Documentation may include test strategy, test plan, test report templates, defect templates, onboarding documents, checklists, and so on.&lt;/p>
&lt;p>This is useful because when you need them, you will know these documents have been reviewed and are up to date. They will not be stale documents that lose their usefulness simply because they are outdated.&lt;/p>
&lt;h2 id="create-or-optimize-automated-tests">Create or Optimize Automated Tests
&lt;/h2>&lt;p>You can use the quiet time to add more automated tests to your test suite. In addition, you can improve your framework structure and optimize existing tests (such as fixing flaky tests, fixing tests that do not work, and improving test steps).&lt;/p>
&lt;p>If you are not using any automation tool yet, you can explore which tools can be used for your product, or you can start automating some small, basic scenarios to see how they work before regular use.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/125-no_test_time/markdown-upload_hu_b4f46d3b2dee063e.webp"
width="1024"
height="768"
srcset="https://chengxiaqiucao.github.io/post/125-no_test_time/markdown-upload_hu_27d7456bd3354e0a.webp 480w, https://chengxiaqiucao.github.io/post/125-no_test_time/markdown-upload_hu_b4f46d3b2dee063e.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="133"
data-flex-basis="320px"
>
&lt;/p>
&lt;h2 id="review-past-bugs-or-production-issues">Review Past Bugs or Production Issues
&lt;/h2>&lt;p>Reviewing old bugs or production issues to see what was missed during testing is very useful. This gives you scenario ideas you can use in future testing. You can add these scenarios to test cases or automation suites to prevent these bugs from happening again.&lt;/p>
&lt;p>Use this time to learn something from these bugs that will help you in the future.&lt;/p>
&lt;h2 id="explore-other-testing-areas">Explore Other Testing Areas
&lt;/h2>&lt;p>If you already have some mature performance and security testing, you can review them, explore different scenarios, and see how the application performs in terms of performance and security.&lt;/p>
&lt;p>If you do not have such tests, you can explore what tools can be used, check whether they would benefit your project, try some of them, and so on.&lt;/p>
&lt;h2 id="invest-in-yourself">Invest in Yourself
&lt;/h2>&lt;p>Quiet time is a great space for your growth. You can use this time to read QA articles or blog posts, watch tutorials that can help you, try new tools, take courses that help your work, and so on. Afterward, you can present what you learned to the team.&lt;/p>
&lt;p>This keeps you inspired, you will learn new things, you will improve, and you will gain new ideas.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/125-no_test_time/tester_prompt_hu_e73bb628a399e84a.webp"
width="1024"
height="576"
srcset="https://chengxiaqiucao.github.io/post/125-no_test_time/tester_prompt_hu_6f3f9ed61a8f9617.webp 480w, https://chengxiaqiucao.github.io/post/125-no_test_time/tester_prompt_hu_e73bb628a399e84a.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="177"
data-flex-basis="426px"
>
&lt;/p>
&lt;h2 id="conclusion">Conclusion
&lt;/h2>&lt;p>As discussed above, even if no one assigns you a testing task today, there is always something to do. By practicing some of these ideas, you will certainly bring more value to the project, the team, and yourself.&lt;/p>
&lt;p>As test engineers, our value is not just in executing test cases. Our value lies in our contribution to product quality, our improvement of processes, and our own professional growth.&lt;/p>
&lt;p>Even on days that seem &amp;ldquo;there is nothing to do&amp;rdquo;, we can find ways to improve ourselves and the team.&lt;/p>
&lt;p>&lt;strong>Testing never ends, and neither does growth.&lt;/strong>&lt;/p></description></item><item><title>Feeling Marginalized by Your Leader at Work? How to Adjust</title><link>https://chengxiaqiucao.github.io/en/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/</link><pubDate>Sun, 20 Jul 2025 00:00:00 +0000</pubDate><guid>https://chengxiaqiucao.github.io/en/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-1.webp" alt="Featured image of post Feeling Marginalized by Your Leader at Work? How to Adjust" />&lt;blockquote>
&lt;p>New to the workplace, I always feel marginalized by my leader, and my state of mind is crumbling — how should I adjust myself?&lt;/p>&lt;/blockquote>
&lt;p>As the saying goes, nine out of ten things in life do not go as one wishes. Many people new to the workplace brim with ambition but have no chance to display it, and can easily feel overlooked or even deliberately marginalized, leading to an unbalanced mindset and endless frustration.&lt;/p>
&lt;p>In this article we briefly discuss this topic.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-1_hu_3a5e92ed827efa3b.webp"
width="1024"
height="550"
srcset="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-1_hu_ff10b8218f0f5557.webp 480w, https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-1_hu_3a5e92ed827efa3b.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="186"
data-flex-basis="447px"
>
&lt;/p>
&lt;h2 id="are-you-really-being-marginalized">Are You Really Being Marginalized?
&lt;/h2>&lt;p>For most people, from childhood through their school years, the path of action was in most cases clear: study hard and you get good grades; whatever you do, the result mostly matches expectations.&lt;/p>
&lt;p>But once you enter the workplace and step into society, things are not quite the same. You work hard and act positively, yet the results may not match your expectations. Not only do you fail to earn your leader&amp;rsquo;s recognition — you may even get a cold splash of water — and it is easy to feel targeted and marginalized.&lt;/p>
&lt;p>So, is this really being marginalized?&lt;/p>
&lt;p>First of all, you should believe that &lt;strong>the so-called marginalization is not a common phenomenon within a team&lt;/strong>.&lt;/p>
&lt;p>People often tend to be self-centered, viewing the things around them from a first-person perspective and focusing on how others respond to their actions. They also tend to act according to their own fixed ways of thinking and understanding — full of enthusiasm, yet not necessarily met with applause.&lt;/p>
&lt;p>In fact, if you shift your perspective and look from the leader&amp;rsquo;s or the team&amp;rsquo;s point of view, problems are often easy to spot. Is your &amp;ldquo;hard work and proactive behavior&amp;rdquo; truly valuable to the team?&lt;/p>
&lt;p>Huawei once had a newly hired graduate student from Peking University who, right after joining, wrote a long, ten-thousand-word letter to Ren Zhengfei, discussing at length his suggestions for the company&amp;rsquo;s future development.&lt;/p>
&lt;p>Ren Zhengfei replied — &lt;em>If this person is mentally ill, it is recommended that he be sent to a hospital for treatment; if he is not ill, it is recommended that he be dismissed&lt;/em>&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720_hu_aa824220ca156e1e.webp"
width="1024"
height="605"
srcset="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720_hu_9cfa9ca0b8b092b1.webp 480w, https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720_hu_aa824220ca156e1e.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="169"
data-flex-basis="406px"
>
&lt;/p>
&lt;p>Looking at it from the team&amp;rsquo;s perspective again, in any team resources are always tight, and human resources are especially precious. In reality, no leader likes to put a capable person on the bench.&lt;/p>
&lt;p>So in many cases, the so-called &amp;ldquo;being marginalized&amp;rdquo; is very likely just an illusion caused by your own sense of letdown. More often, once you find the crux of the problem and make the adjustment, you can move past it.&lt;/p>
&lt;h2 id="how-to-adjust">How to Adjust?
&lt;/h2>&lt;p>So how do you better adapt to the team and find your place?&lt;/p>
&lt;p>It is really what was mentioned earlier — &lt;strong>aligning your personal value and the team&amp;rsquo;s value in the same direction&lt;/strong>.&lt;/p>
&lt;p>If the so-called marginalization is mostly because you have not yet delivered the value you should, then find the corresponding cause and make targeted improvements.&lt;/p>
&lt;p>There may be various reasons for not delivering value:&lt;/p>
&lt;ul>
&lt;li>Business capability — work hard to improve your professional skills and learn with an open mind&lt;/li>
&lt;li>Collaboration — in teamwork you cannot be a lone wolf; maintain smooth cooperation with your teammates&lt;/li>
&lt;li>Personal reasons — put simply, you overrate yourself and are ambitious but inexperienced; you think you deserve a certain position, but your actual ability and influence are not yet up to it&lt;/li>
&lt;/ul>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-2_hu_57bdec4e1bd21c2c.webp"
width="1024"
height="702"
srcset="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-2_hu_3a9efbaf01b81f3d.webp 480w, https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-2_hu_57bdec4e1bd21c2c.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="145"
data-flex-basis="350px"
>
&lt;/p>
&lt;p>And to determine where the crux lies, besides your own observation and attempts, the more effective approach is &lt;strong>direct communication&lt;/strong> with your leader.&lt;/p>
&lt;p>Understand your leader&amp;rsquo;s (team&amp;rsquo;s) expectations of you, clarify what your position, the work you take on, and your effective output are, and then make targeted changes.&lt;/p>
&lt;h2 id="really-being-marginalized">Really Being Marginalized
&lt;/h2>&lt;p>Of course, wherever there are people there is a &amp;ldquo;world&amp;rdquo; of its own, and we cannot rule out the possibility that you are genuinely considered not worth cultivating by your leader and really are marginalized.&lt;/p>
&lt;p>But even so, there is no need to be too discouraged — there is still room.&lt;/p>
&lt;p>Because, looking at the different situations of members within a team, &lt;strong>being marginalized&lt;/strong> may not be the worst case.&lt;/p>
&lt;p>Within a team, members can roughly be divided into the following types:&lt;/p>
&lt;ul>
&lt;li>High-value employees can take charge of key work and core business, and enjoy various incentives tilted in their favor&lt;/li>
&lt;li>Average-value employees mainly handle routine work, assist in the completion of core business, and receive the team&amp;rsquo;s normal incentives&lt;/li>
&lt;li>Low-value employees, that is, &amp;ldquo;marginalized&amp;rdquo; employees, usually do peripheral work that does not affect the team&amp;rsquo;s development and rarely receive incentives&lt;/li>
&lt;li>Negative-value employees are those awaiting elimination and need to be removed from the team as early as possible&lt;/li>
&lt;/ul>
&lt;p>And being marginalized, although fairly dangerous within a team, does not go so far as elimination; it can be said to be in a &lt;strong>probationary period&lt;/strong>.&lt;/p>
&lt;p>At this point, through direct communication with your leader, &lt;strong>finding where the gap between your own and the team&amp;rsquo;s expectations lies and making targeted changes&lt;/strong>, you have a chance to return to the right position.&lt;/p>
&lt;p>Naturally, another situation is that through communication you discover the result cannot be changed:&lt;/p>
&lt;ul>
&lt;li>The team&amp;rsquo;s positioning of you is not what you want, and you are unwilling to match the team&amp;rsquo;s expectations&lt;/li>
&lt;li>Your personal values and the team&amp;rsquo;s (leader&amp;rsquo;s) values differ greatly to begin with — in short, you are not on the same page&lt;/li>
&lt;li>The constraints on you as an individual are too great, affecting your further development&lt;/li>
&lt;/ul>
&lt;p>At this point, either adjust your own mindset and settle into being marginalized — for one without desires there is no weakness — or quietly grow, wait for the right opportunity, build up strength for a later surge, and seek another place where you belong.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-3_hu_69b599408965d0e2.webp"
width="1024"
height="781"
srcset="https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-3_hu_ba15e3324c7a98b9.webp 480w, https://chengxiaqiucao.github.io/post/112-%E8%A2%AB%E8%BE%B9%E7%BC%98%E5%8C%96/Pasted-20250720-3_hu_69b599408965d0e2.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="131"
data-flex-basis="314px"
>
&lt;/p>
&lt;h2 id="conclusion">Conclusion
&lt;/h2>&lt;p>All in all, if you feel &amp;ldquo;marginalized&amp;rdquo; in the workplace, do not be anxious — in many cases it is not what you think it is. Have a good talk with your superior, find out where the crux lies, and a turning point may well be right in front of you.&lt;/p></description></item><item><title>How Is the IT Job Market for 2025 Graduates?</title><link>https://chengxiaqiucao.github.io/en/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/</link><pubDate>Sat, 28 Jun 2025 14:25:06 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/title.webp" alt="Featured image of post How Is the IT Job Market for 2025 Graduates?" />&lt;h2 id="the-toughest-job-hunting-season-ever">The Toughest Job-Hunting Season Ever
&lt;/h2>&lt;p>The slogan &amp;ldquo;the toughest job-hunting season ever&amp;rdquo; is repeated every year, but for the class of 2025, this seems to be no longer just a slogan.&lt;/p>
&lt;p>According to Baidu&amp;rsquo;s forecast data, against the backdrop of year-on-year enrollment expansion in universities, the number of college graduates in 2025 has reached a staggering &lt;strong>12.22 million&lt;/strong> (compared with &lt;strong>9.54 million&lt;/strong> newborns in 2024 &amp;lt;&lt;code>2024 Government Economic and Social Development Statistical Bulletin&lt;/code>&amp;gt;, the halo of a university degree has long since faded), and the pressure on the supply side of employment has hit a historic peak!&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628-1_hu_9c7f4cfedb0465d1.webp"
width="1024"
height="883"
srcset="https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628-1_hu_a8304c63e76d6fc5.webp 480w, https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628-1_hu_9c7f4cfedb0465d1.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="116"
data-flex-basis="278px"
>
&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628-2_hu_fcff3553b92771e2.webp"
width="1024"
height="557"
srcset="https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628-2_hu_71745a33bbbd4ede.webp 480w, https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628-2_hu_fcff3553b92771e2.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="183"
data-flex-basis="441px"
>
&lt;/p>
&lt;p>And according to the latest report from Zhaopin, the overall employment rate of college graduates (including flexible employment) is currently only &lt;strong>55.5%&lt;/strong>. For many graduates, &amp;ldquo;graduation means unemployment&amp;rdquo; seems to have become a bitter reality!&lt;/p>
&lt;h2 id="a-tale-of-two-extremes-in-it-employment">A Tale of Two Extremes in IT Employment
&lt;/h2>&lt;p>With the explosive growth of industries such as AI and intelligent driving, demand in the IT sector remains strong, yet it also clearly shows a trend of polarization! On one hand, emerging fields such as artificial intelligence and cybersecurity are short of talent; on the other hand, traditional internet positions are shrinking, and the competition ratio for some positions exceeds &lt;strong>100:1&lt;/strong>&lt;/p>
&lt;h3 id="it-is-still-a-guarantee-of-good-pay">IT Is Still a Guarantee of Good Pay
&lt;/h3>&lt;p>According to data from the 2024 national statistical yearbook, the IT industry, with an average annual salary of &lt;strong>231,800 yuan&lt;/strong>, has topped the industry pay rankings for nine consecutive years&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628_hu_d56f423a65ab65c3.webp"
width="1024"
height="803"
srcset="https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628_hu_a123ebd40528f233.webp 480w, https://chengxiaqiucao.github.io/post/103-%E9%AB%98%E6%A0%A1it%E5%B0%B1%E4%B8%9A/Pasted-20250628_hu_d56f423a65ab65c3.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="127"
data-flex-basis="306px"
>
&lt;/p>
&lt;h3 id="falling-employment-rates-and-rising-education-barriers">Falling Employment Rates and Rising Education Barriers
&lt;/h3>&lt;p>The overall employment rate for computer science undergraduates of the class of 2024 fell to &lt;strong>68.65%&lt;/strong>, and some universities saw extreme cases of &amp;ldquo;only 200 out of 600 students employed&amp;rdquo;. For core positions at major tech firms (algorithm, R&amp;amp;D, etc.), over 60% &lt;strong>require a master&amp;rsquo;s degree&lt;/strong>, and students from 985/211 universities, backed by university-enterprise collaboration resources, find it easier to land high-paying opportunities. ( &lt;a class="link" href="http://www.360doc.com/content/25/0622/14/7938234_1155996907.shtml" target="_blank" rel="noopener"
>Data Source&lt;/a>)&lt;/p>
&lt;h3 id="widening-salary-polarization">Widening Salary Polarization
&lt;/h3>&lt;ul>
&lt;li>&lt;strong>Top tier&lt;/strong>: algorithm roles at major tech firms pay &lt;strong>400,000-500,000 yuan&lt;/strong> annually, while top AI talent can earn &lt;strong>800,000-1.5 million yuan&lt;/strong> a year&lt;/li>
&lt;li>&lt;strong>Ordinary tier&lt;/strong>: undergraduates from ordinary colleges generally earn a monthly salary of &lt;strong>7K-10K&lt;/strong>, and some are forced to change careers or &amp;ldquo;downshift&amp;rdquo; to second-tier cities&lt;/li>
&lt;li>&lt;strong>Industry comparison&lt;/strong>: the IT industry, with an average annual wage of &lt;strong>231,800 yuan&lt;/strong>, has ranked first among all industries for nine consecutive years, yet the average monthly salary of computer science undergraduates of the class of 2023, &lt;strong>6,771 yuan&lt;/strong>, was overtaken for the first time by electronic information majors (6,802 yuan)&lt;/li>
&lt;/ul>
&lt;h3 id="saturation-of-traditional-positions">Saturation of Traditional Positions
&lt;/h3>&lt;p>Java back-end and basic development roles have become a &amp;ldquo;&lt;strong>red ocean&lt;/strong>&amp;rdquo; due to fierce competition, with resume submission ratios at small and medium-sized enterprises reaching &lt;strong>8:1&lt;/strong>27. Salaries for junior development positions have fallen back to &lt;strong>8-12K&lt;/strong>, and many companies have begun to exhibit the phenomenon of &amp;ldquo;hiring at lower pay&amp;rdquo;.&lt;/p>
&lt;h4 id="explosive-shortage-of-high-end-talent">Explosive Shortage of High-End Talent
&lt;/h4>&lt;ul>
&lt;li>&lt;strong>Artificial intelligence&lt;/strong>: the talent gap exceeds &lt;strong>5 million&lt;/strong>, with a supply-demand ratio of &lt;strong>1:10&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Cybersecurity&lt;/strong>: only 30,000 people are trained each year, yet the &lt;strong>position gap is as high as 700,000&lt;/strong>, a gap rate of &lt;strong>95%&lt;/strong>, and the shortfall is expected to widen to &lt;strong>3.27 million&lt;/strong> by 2027&lt;/li>
&lt;li>&lt;strong>Hard-tech fields&lt;/strong>: demand for domestic innovation and local-substitution positions such as chip design and industrial software is growing by &lt;strong>15%+&lt;/strong> annually&lt;/li>
&lt;/ul>
&lt;h2 id="self-help-strategies">Self-Help Strategies
&lt;/h2>&lt;p>So, under such employment conditions, how can current graduates — or students about to enter the job market — break through?&lt;/p>
&lt;h3 id="target-high-growth-fields-and-seek-blue-ocean-opportunities">Target High-Growth Fields and Seek Blue-Ocean Opportunities
&lt;/h3>&lt;ul>
&lt;li>&lt;strong>Cybersecurity&lt;/strong>: obtain the &lt;strong>NISP Level 2 certificate&lt;/strong> (which can be exchanged for CISP without an exam); certificate holders enjoy priority hiring by enterprises and subsidies from local governments&lt;/li>
&lt;li>&lt;strong>AI application layer&lt;/strong>: focus on real-world scenarios such as autonomous driving, medical imaging, and quantitative finance&lt;/li>
&lt;li>&lt;strong>Hard tech&lt;/strong>: embedded development (IoT), domestic substitution of industrial software&lt;/li>
&lt;/ul>
&lt;h3 id="build-compound-skills">Build Compound Skills
&lt;/h3>&lt;p>&amp;ldquo;&lt;strong>Computer Science + X&lt;/strong>&amp;rdquo; compound talents earn &lt;strong>20%&lt;/strong> more than purely technical roles, for example:&lt;/p>
&lt;ul>
&lt;li>FinTech (quantitative models)&lt;/li>
&lt;li>Bioinformatics (gene sequencing)&lt;/li>
&lt;li>Smart agriculture (sensor technology)&lt;/li>
&lt;/ul>
&lt;h3 id="back-yourself-with-hands-on-experience">Back Yourself with Hands-On Experience
&lt;/h3>&lt;ul>
&lt;li>&lt;strong>Internships at major tech firms&lt;/strong>: the conversion-to-full-time rate exceeds &lt;strong>50%&lt;/strong>, and summer internships have become a core springboard&lt;/li>
&lt;li>&lt;strong>Project experience&lt;/strong>: high-star GitHub projects, Kaggle competition rankings, and university-enterprise collaboration project experience&lt;/li>
&lt;li>&lt;strong>Certification boost&lt;/strong>: certifications such as cloud-native (Kubernetes) and penetration testing (CISP-PTE)&lt;/li>
&lt;/ul>
&lt;h4 id="make-rational-regional-choices">Make Rational Regional Choices
&lt;/h4>&lt;p>New first-tier cities offer outstanding value for money: IT salaries in places such as Suzhou and Xi&amp;rsquo;an reach &lt;strong>60%-80%&lt;/strong> of those in first-tier cities, while living costs are &lt;strong>30%-50%&lt;/strong> lower.&lt;/p>
&lt;h2 id="conclusion">Conclusion
&lt;/h2>&lt;p>For graduates who stay in their comfort zone and have only a single skill, the 2025 IT job market is undoubtedly a cold winter; but for those who actively embrace change, proactively learn cutting-edge technologies, and develop the ability to solve complex problems, it is also a golden age full of boundless opportunities.&lt;/p>
&lt;p>The challenges are real, and the future will always belong to those who take the initiative!&lt;/p></description></item><item><title>Can You Still Work in Testing Without Coding Skills</title><link>https://chengxiaqiucao.github.io/en/post/065-%E6%B2%A1%E4%BB%A3%E7%A0%81%E8%83%BD%E5%8A%9B%E8%BF%98%E8%83%BD%E5%90%A6%E4%BB%8E%E4%BA%8B%E6%B5%8B%E8%AF%95%E5%B7%A5%E4%BD%9C/</link><pubDate>Sat, 15 Mar 2025 00:04:55 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/065-%E6%B2%A1%E4%BB%A3%E7%A0%81%E8%83%BD%E5%8A%9B%E8%BF%98%E8%83%BD%E5%90%A6%E4%BB%8E%E4%BA%8B%E6%B5%8B%E8%AF%95%E5%B7%A5%E4%BD%9C/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/065-%E6%B2%A1%E4%BB%A3%E7%A0%81%E8%83%BD%E5%8A%9B%E8%BF%98%E8%83%BD%E5%90%A6%E4%BB%8E%E4%BA%8B%E6%B5%8B%E8%AF%95%E5%B7%A5%E4%BD%9C/Pasted-20250316.webp" alt="Featured image of post Can You Still Work in Testing Without Coding Skills" />&lt;blockquote>
&lt;p>Many people from non-IT backgrounds who want to switch to testing have heard it said that software testing has a low barrier to entry—that you can get into the industry even without knowing how to code. So is that actually the case?&lt;/p>&lt;/blockquote>
&lt;p>The answer should be stated plainly:&lt;/p>
&lt;p>&lt;strong>Without coding skills, you actually can work in software testing—and yet, in practice, you actually cannot.&lt;/strong>&lt;/p>
&lt;h2 id="why-you-actually-can">Why you actually can
&lt;/h2>&lt;p>Software testing is not a discipline built on coding ability, which is why, in principle, you can do it.&lt;/p>
&lt;p>Software testing is the act of exposing quality problems in a product through testing; it is, in essence, a skill of discovering the unknown. What matters more, then, are abilities such as experimentation, exploration, observation, reasoning, questioning, and modeling. Having coding skills, on the other hand, mostly helps you understand how the product is implemented, or lets you use code to extend your testing methods and improve testing efficiency. In this sense, coding ability is a supporting capability—one that assists the testing work, but is by no means the decisive factor in whether that work can be accomplished!&lt;/p>
&lt;p>In his paper &amp;ldquo;Testing and Checking&amp;rdquo;, James Bach elaborated on the relationship between &lt;code>testing&lt;/code> and &lt;code>checking&lt;/code>&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/065-%E6%B2%A1%E4%BB%A3%E7%A0%81%E8%83%BD%E5%8A%9B%E8%BF%98%E8%83%BD%E5%90%A6%E4%BB%8E%E4%BA%8B%E6%B5%8B%E8%AF%95%E5%B7%A5%E4%BD%9C/testing-checking_hu_dd929c89bdafaa47.webp"
width="1024"
height="782"
srcset="https://chengxiaqiucao.github.io/post/065-%E6%B2%A1%E4%BB%A3%E7%A0%81%E8%83%BD%E5%8A%9B%E8%BF%98%E8%83%BD%E5%90%A6%E4%BB%8E%E4%BA%8B%E6%B5%8B%E8%AF%95%E5%B7%A5%E4%BD%9C/testing-checking_hu_49031c7ebfaab54e.webp 480w, https://chengxiaqiucao.github.io/post/065-%E6%B2%A1%E4%BB%A3%E7%A0%81%E8%83%BD%E5%8A%9B%E8%BF%98%E8%83%BD%E5%90%A6%E4%BB%8E%E4%BA%8B%E6%B5%8B%E8%AF%95%E5%B7%A5%E4%BD%9C/testing-checking_hu_dd929c89bdafaa47.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="130"
data-flex-basis="314px"
>
&lt;/p>
&lt;p>&lt;code>testing&lt;/code> is the broader concept, while &lt;code>checking&lt;/code> is only a subset of testing—and checking itself is further divided into manual checking and checking performed with the help of machines (tools).&lt;/p>
&lt;p>What coding ability affects, then, falls mostly within that tool-assisted checking part.&lt;/p>
&lt;p>That is why, in the early days, many testing experts who excelled at the work were not particularly good at coding; more often than not, they were domain experts in the relevant business area, equipped with outstanding testing thinking—that is, the detective-like abilities of observation and reasoning mentioned above.&lt;/p>
&lt;p>So, in truth, lacking coding skills does not prevent you from doing testing work exceptionally well.&lt;/p>
&lt;h2 id="why-you-actually-cannot">Why you actually cannot
&lt;/h2>&lt;p>And yet, we must also say that, without coding skills, in practice you really cannot.&lt;/p>
&lt;p>As we noted above, in the &lt;strong>early days&lt;/strong> there were indeed testing experts who could not code. But times have changed, and the reality today is quite different. As the industry has evolved, the direction of the testing profession has arguably departed from its original track. It is rather lamentable, and worthy of a sigh!&lt;/p>
&lt;p>There are several reasons:&lt;/p>
&lt;h3 id="the-rise-of-development-models-that-emphasize-fast-delivery-such-as-agile">The rise of development models that emphasize fast delivery, such as Agile
&lt;/h3>&lt;p>In Agile development models, there is in fact no longer a dedicated testing role; instead, the emphasis is on team members being versatile generalists who can take on a range of development tasks with one specialty and many skills—including both development and testing. As a member of the team, a tester naturally cannot do testing alone; when necessary, they must also be able to pick up development work, at least including tasks originally in the developer&amp;rsquo;s domain such as unit testing and integration testing. Coding ability is, of course, the hard requirement for meeting this condition.&lt;/p>
&lt;h3 id="the-mandatory-requirement-for-test-automation-skills">The mandatory requirement for test automation skills
&lt;/h3>&lt;p>Also driven by the needs of development models such as Agile and continuous integration, test automation has become an indispensable part of the process. And as the foundational capability for test automation, coding ability is naturally a necessity.&lt;/p>
&lt;p>&lt;em>But it must be pointed out here that something like test automation—aimed at &amp;ldquo;quickly completing testing&amp;rdquo;—is, according to the relationship between testing and checking shown in the figure above, not really &amp;ldquo;testing&amp;rdquo; at all; it is much more &amp;ldquo;checking&amp;rdquo;. A single-minded emphasis on coding ability is, in a sense, actually a weakening of the requirements of testing work—that is, it increasingly demands only &amp;ldquo;checking&amp;rdquo; rather than &amp;ldquo;testing&amp;rdquo;.&lt;/em>&lt;/p>
&lt;h3 id="the-talent-market-is-oversupplied">The talent market is oversupplied
&lt;/h3>&lt;p>Finally, there is the industry environment. In the early days of the internet boom, the talent gap was large, and a great deal of &amp;ldquo;verification&amp;rdquo; work was done manually by junior staff or complete beginners with zero foundation who did not need coding skills; manual &amp;ldquo;checking&amp;rdquo; accounted for a larger share.&lt;/p>
&lt;p>But when the industry turns downward, companies cut costs, leading to an oversupplied talent market. The entry barrier naturally rises, job requirements climb accordingly, and expectations for tool-based &amp;ldquo;verification&amp;rdquo; grow higher—so coding ability, test automation, tool development, and the like have all but become must-have skills.&lt;/p>
&lt;p>Layered on top of that is the current prevalence of development models such as Agile and the resulting demand for test automation. It is fair to say that, without coding skills, in today&amp;rsquo;s environment it has become very hard to argue that one can still work in testing—there is simply no way in.&lt;/p>
&lt;h2 id="conclusion">Conclusion
&lt;/h2>&lt;p>So, under present conditions, when it comes to testing work, lacking coding skills does not mean you cannot accomplish the work—but without coding ability it has become very difficult to get on board.&lt;/p>
&lt;p>Therefore, as individuals swept along by the tide of the times, what we can do is not to swim against the current, but to steadily build personal capabilities that move with the trend.
But we must still understand what the core requirements of this work truly are—accumulate steadily and then burst forth, for gold only appears after all the sand is washed away!&lt;/p></description></item><item><title>How to Handle Conflicts Between Developers and Testers</title><link>https://chengxiaqiucao.github.io/en/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/</link><pubDate>Wed, 19 Feb 2025 12:28:00 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-2.webp" alt="Featured image of post How to Handle Conflicts Between Developers and Testers" />&lt;blockquote>
&lt;p>A reader asked: on a team, developers and testers often run into friction and conflict — how do we avoid such conflicts within the team?&lt;/p>&lt;/blockquote>
&lt;h1 id="the-origin-of-conflict">The Origin of Conflict
&lt;/h1>&lt;p>In a team, conflict between members is actually perfectly normal and very hard to eliminate entirely. The causes vary, but in poor teams conflicts are more likely to arise: mismatched goals and expectations, lack of trust, and poor communication are all common reasons that conflicts arise and even escalate.&lt;/p>
&lt;h1 id="must-conflict-always-be-avoided">Must Conflict Always Be Avoided?
&lt;/h1>&lt;p>From the standpoint of the project and the product, the friction and conflict between developers and testers isn&amp;rsquo;t entirely a bad thing. Nor should we take it for granted that conflict must always be avoided.&lt;/p>
&lt;p>In many R&amp;amp;D project management practices, the conflict between developers and testers is called constructive conflict — that is, this kind of conflict is constructive for improving product quality, and product quality gets improved through the two sides&amp;rsquo; conflict-focused discussions on specific issues.&lt;/p>
&lt;p>This idea in fact aligns with how conflict management classifies conflict types.&lt;/p>
&lt;p>In conflict management theory, using the two dimensions of how important the matter behind the conflict is and the interpersonal relationship, conflict types can be divided into the following four categories:&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-1_hu_9c16675ad641f7d9.webp"
width="1024"
height="786"
srcset="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-1_hu_827295a4fc851e8b.webp 480w, https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220-1_hu_9c16675ad641f7d9.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="130"
data-flex-basis="312px"
>
&lt;/p>
&lt;ul>
&lt;li>
&lt;p>&lt;strong>Constructive conflict&lt;/strong>: The conflict is task-related, usually aimed at solving a problem, with little impact on the interpersonal relationship between the two sides. This kind of conflict is actually healthy.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Destructive conflict&lt;/strong>: The conflict is also aimed at solving a problem, but it is more intense and damaging to the relationship, affecting friendly cooperation down the line.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Dysfunctional conflict&lt;/strong>: This one is worse — caused purely by the estrangement between the two sides, with little to do with disagreement over the matter itself; you could call it conflict for conflict&amp;rsquo;s sake.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>&lt;strong>Functional conflict&lt;/strong>: This is the most common kind, directed at trivial matters and usually showing up as grumbling, joking complaints, and the like.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>For the different conflict types, a team should generally encourage constructive conflict, stop destructive conflict promptly, isolate dysfunctional conflict, and tolerate functional conflict while keeping it from accumulating.&lt;/p>
&lt;h1 id="the-thomas-kilmann-conflict-model">The Thomas-Kilmann Conflict Model
&lt;/h1>&lt;p>For individuals, there is also a theoretical model for how to handle conflict — the Thomas-Kilmann conflict management model:&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220_hu_148e1d87e68b7485.webp"
width="1024"
height="576"
srcset="https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220_hu_ab13167beeb5b84a.webp 480w, https://chengxiaqiucao.github.io/post/056-%E5%9B%A2%E9%98%9F%E4%B8%AD%E7%9A%84%E5%86%B2%E7%AA%81%E7%AE%A1%E7%90%86/Pasted-20250220_hu_148e1d87e68b7485.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="177"
data-flex-basis="426px"
>
&lt;/p>
&lt;p>From two dimensions when facing conflict — your personal assertiveness in solving the problem and your cooperativeness in managing the relationship with the other party — come the following five conflict-handling strategies:&lt;/p>
&lt;p>&lt;strong>Competing&lt;/strong>: When an individual is assertive, they can adopt a competing strategy. It creates a win-or-lose situation, where the stronger party forces the other to accept their demands. &lt;strong>Win-Lose&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Collaborating&lt;/strong>: This is the best strategy — through cooperation and teamwork, both sides find a win-win path where 1+1&amp;gt;2. &lt;strong>Win-Win&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Avoiding&lt;/strong>: Does not solve the problem; a cold treatment that shelves the issue. &lt;strong>Lose-Lose&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Accommodating&lt;/strong>: One side voluntarily yields in order to preserve the relationship. &lt;strong>Lose-Win&lt;/strong>&lt;/p>
&lt;p>&lt;strong>Compromising&lt;/strong>: Meeting in the middle — both sides give a little and make mutual concessions to reach a middle-ground solution, forming a compromise. &lt;strong>Half-Half&lt;/strong>&lt;/p>
&lt;p>Different individuals, when facing conflict, consciously or unconsciously adopt different strategies. Understanding this model helps us assess conflicts more rationally and choose an appropriate way to respond.&lt;/p>
&lt;h1 id="how-should-a-team-manage-conflict">How Should a Team Manage Conflict?
&lt;/h1>&lt;p>For an R&amp;amp;D team, managing conflict well fundamentally comes down to building a strong team culture on the foundation of sound processes and systems, and fostering a transparent, trust-based cooperative relationship and environment.&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Sound systems. For example, disputes over bugs should have an arbitration mechanism, rather than leaving developers and testers to argue themselves red in the face.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Team culture. Testing and development work should not be set against each other; instead, everyone collaborates toward a shared quality goal.&lt;/p>
&lt;/li>
&lt;/ul></description></item><item><title>Choosing Between Testing and Development</title><link>https://chengxiaqiucao.github.io/en/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/</link><pubDate>Sun, 03 Nov 2024 23:54:39 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/</guid><description>&lt;blockquote>
&lt;p>When asked in an interview, why did you choose to go into testing rather than development?&lt;/p>&lt;/blockquote>
&lt;h2 id="what-is-actually-being-asked">What Is Actually Being Asked?
&lt;/h2>&lt;p>The question implies that the interview is for a testing position. And the interviewer&amp;rsquo;s question really has two reasons behind it:&lt;/p>
&lt;p>First, to determine whether the candidate made the choice proactively or was pushed into it.&lt;/p>
&lt;p>Proactive: they have their own ideas and set their sights on a testing role from the start.&lt;/p>
&lt;p>Passive: they would actually rather do development, but their programming skills are insufficient, and algorithms, design patterns, and the like are a mess.&lt;/p>
&lt;p>Second, to see how well the candidate understands the core requirements of these two roles.&lt;/p>
&lt;h2 id="how-should-you-respond">How Should You Respond?
&lt;/h2>&lt;p>Once you understand the purpose behind the question, the strategy for responding becomes clear:&lt;/p>
&lt;p>First of all, of course, you should show the interviewer that you considered this role proactively. And the reason you considered it is precisely your own understanding of testing work.&lt;/p>
&lt;p>For example, in one of my previous answers:&lt;/p>
&lt;p>&lt;a class="link" href="https://chengxiaqiucao.github.io/post/07-%E5%88%B0%E5%BA%95%E4%BB%80%E4%B9%88%E6%98%AF%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E7%9B%AE%E7%9A%84/" target="_blank" rel="noopener"
>What Is the Purpose of Software Testing?&lt;/a>&lt;/p>
&lt;p>The testing role actually calls for many qualities different from development work, such as being good at questioning, paying attention to detail, and enjoying digging down to the root of things.&lt;/p>
&lt;p>In Jame Bach&amp;rsquo;s discussion of the difference between testing and checking, he in fact also points out many of the special abilities that testing work requires.&lt;/p>
&lt;p>&lt;img src="https://picx.zhimg.com/80/v2-76b121b6af77ba6f4b7aa827ac815fce_1440w.png"
loading="lazy"
>
&lt;/p>
&lt;p>Beyond that, you can also demonstrate some of the accumulation you have in testing-related areas — for instance, a solid grasp of testing tools and test automation; and if you have relevant, presentable project experience, that is all the more convincing. The implicit message here is that you did not choose against development because you lack programming ability or cannot do development, but simply because your interests lie more on the testing side.&lt;/p>
&lt;p>As for the differences between these two roles, testing and development, you can also elaborate from angles such as these:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Development weeds through the old to bring forth the new, while testing holds that nothing can be built without first being broken.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Development work pursues certainty, whereas testing is grounded in uncertainty.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Development emphasizes creation, while testing excels at digging into unexpected side branches.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>And so on&amp;hellip;
&lt;img src="https://chengxiaqiucao.github.io/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/Pasted-20241104-1_hu_5cadf1e56d3abf4e.webp"
width="1024"
height="564"
srcset="https://chengxiaqiucao.github.io/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/Pasted-20241104-1_hu_aeb0f1a55247c49c.webp 480w, https://chengxiaqiucao.github.io/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/Pasted-20241104-1_hu_5cadf1e56d3abf4e.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="181"
data-flex-basis="435px"
>
&lt;/p>
&lt;h2 id="a-note">A Note
&lt;/h2>&lt;p>All the above speaks of response strategies, but it is best if you genuinely lean toward this job because of the nature of testing work itself, rather than settling for it as a second choice.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/Pasted-20241104_hu_58fc9c538a43eefb.webp"
width="1024"
height="941"
srcset="https://chengxiaqiucao.github.io/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/Pasted-20241104_hu_d74d133b5c91f9e.webp 480w, https://chengxiaqiucao.github.io/post/046-%E6%B5%8B%E8%AF%95%E5%92%8C%E5%BC%80%E5%8F%91%E7%9A%84%E9%80%89%E6%8B%A9/Pasted-20241104_hu_58fc9c538a43eefb.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="108"
data-flex-basis="261px"
>
&lt;/p></description></item><item><title>The Importance of Communication in Team Management</title><link>https://chengxiaqiucao.github.io/en/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/</link><pubDate>Mon, 28 Oct 2024 15:18:27 +0800</pubDate><guid>https://chengxiaqiucao.github.io/en/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028-1.webp" alt="Featured image of post The Importance of Communication in Team Management" />&lt;p>In any team, communication is in fact the core work of a manager. What we call management — turning various management methods and ideas into a team&amp;rsquo;s ability to execute — is actually accomplished through communication.&lt;/p>
&lt;p>Managers need to invest a great deal of energy in team communication. Communication is the bridge and the connection, and the inevitable path to holding a team together. But communication is by no means as simple as the two parties just having a chat.&lt;/p>
&lt;h2 id="the-communication-funnel">The Communication Funnel
&lt;/h2>&lt;p>Communication is essentially a process of transmitting information and building consensus, but in communication between people there exists a rule known as the &lt;strong>communication funnel&lt;/strong>.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028_hu_9de310228bb8a02e.webp"
width="1024"
height="948"
srcset="https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028_hu_f00176fa17760f2.webp 480w, https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028_hu_9de310228bb8a02e.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="108"
data-flex-basis="259px"
>
&lt;/p>
&lt;ul>
&lt;li>
&lt;p>If what you have in mind, about the matter we want to communicate, is originally 100% of the information,&lt;/p>
&lt;/li>
&lt;li>
&lt;p>then after it is expressed orally or in writing, the information actually conveyed may be only 80%,&lt;/p>
&lt;/li>
&lt;li>
&lt;p>and the information the other party is able to receive drops to 60%,&lt;/p>
&lt;/li>
&lt;li>
&lt;p>even within the information received, what can be correctly understood without distortion is estimated to be only 40% left,&lt;/p>
&lt;/li>
&lt;li>
&lt;p>and when the relevant information is then translated into concrete action, it drops a further 20%,&lt;/p>
&lt;/li>
&lt;li>
&lt;p>as time passes, it may even decay to almost nothing&amp;hellip;&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>So the transmission of information in fact has a marked attenuation effect, and dealing with the attenuation of this communication funnel is the core of communication management in team management.&lt;/p>
&lt;p>This includes confirmation at multiple levels; checking for deviations through the definition of processes and the setting of milestones and checkpoints; and regular retrospectives to review lessons learned.&lt;/p>
&lt;h2 id="effective-communication-model---the-johari-window">Effective Communication Model - The Johari Window
&lt;/h2>&lt;p>To counter this attenuation effect in communication, to ensure that both parties in a conversation can fully understand one another and reach consensus, and to improve the effectiveness of communication as much as possible on a shared foundation, there is a well-known model: the &lt;strong>Johari Window communication model&lt;/strong>.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028-1_hu_292c012b3ead4da.webp"
width="1024"
height="541"
srcset="https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028-1_hu_86624e3024d75c62.webp 480w, https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028-1_hu_292c012b3ead4da.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="189"
data-flex-basis="453px"
>
&lt;/p>
&lt;p>In this model, based on how well the two parties in communication grasp the information, it is divided into four quadrants.&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Information that I know and you also know lies in the &lt;strong>Open Area&lt;/strong>. In this region, the two parties share the same foundation of information, which is also the basis for building trust when we communicate; the larger this area, the less likely misunderstandings are to arise, and the more it helps us achieve efficient communication.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Information that I know but you do not know lies in the &lt;strong>Hidden Area&lt;/strong>. Everyone has secrets, a real self concealed beneath the surface. But sometimes, to achieve effective communication, appropriately opening up the Hidden Area is a shortcut to winning others&amp;rsquo; trust and building efficient communication.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Information that others know but you do not know — such as others&amp;rsquo; true opinions of you, some of your personal weaknesses, or information you simply do not possess — all belongs to the &lt;strong>Blind Spot Area&lt;/strong> of information. The smaller the Blind Spot Area, the closer your judgment of things is to reality, and the greater the chance of making correct decisions. Keep an exploratory spirit and strive to shrink your own Blind Spot Area. &lt;code>stay foolish, stay hungry&lt;/code>&lt;/p>
&lt;/li>
&lt;li>
&lt;p>The Unknown Area is information that neither party understands. Information in this region is both a risk and a potential source of growth for the team.&lt;/p>
&lt;/li>
&lt;/ul>
&lt;p>In the Johari Window, achieving efficient communication really comes down to four sentences:&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028-2_hu_5a3cd6afda9f6136.webp"
width="1024"
height="888"
srcset="https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028-2_hu_95ea1c8fbbc62410.webp 480w, https://chengxiaqiucao.github.io/post/043-%E5%9B%A2%E9%98%9F%E7%AE%A1%E7%90%86%E4%B8%AD%E6%B2%9F%E9%80%9A%E7%9A%84%E9%87%8D%E8%A6%81%E6%80%A7/Pasted-20241028-2_hu_5a3cd6afda9f6136.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="115"
data-flex-basis="276px"
>
&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Expand the Open Area: the larger the Open Area, the more consensus everyone shares and the easier it is to reach agreement. It is the foundation of mutual trust.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Open the Hidden Area: an effective means of strengthening mutual trust; opening the Hidden Area can also help us expand the Open Area.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Shrink the Blind Spot Area: it helps us understand the facts better, broaden self-awareness, and improve ourselves.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Explore the Unknown Area: encourage open input and fully grasp information from multiple angles and channels, so as to eliminate unknown risks as much as possible.&lt;/p>
&lt;/li>
&lt;/ul></description></item><item><title>Software Testing Roles and Career Prospects</title><link>https://chengxiaqiucao.github.io/en/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/</link><pubDate>Fri, 11 Oct 2024 00:00:00 +0000</pubDate><guid>https://chengxiaqiucao.github.io/en/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/</guid><description>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/TestingCareer.webp" alt="Featured image of post Software Testing Roles and Career Prospects" />&lt;p>Lately I am often asked about the prospects of the software testing industry, and there is no shortage of voices online declaring the decline of testing. Many people choosing a career direction are also quite confused about whether they should enter this profession.&lt;/p>
&lt;p>So I am starting this post to talk about Qiucao&amp;rsquo;s understanding of what the software testing role requires, as well as my views on the profession&amp;rsquo;s prospects.&lt;/p>
&lt;h2 id="what-kind-of-role-is-software-testing-really">What Kind of Role Is Software Testing, Really?
&lt;/h2>&lt;p>To choose an industry, you first have to understand why that industry exists and what value it actually provides.&lt;/p>
&lt;p>As a technical branch of the software industry, software testing is a role oriented toward software quality.&lt;/p>
&lt;p>The reason this profession exists is that quality, as one of the core attributes of a product, needs to be guaranteed to the greatest extent possible. Testing work is what, before a product is delivered to users, completes the assessment of product quality and exposes potential quality problems in the product as much as possible, so that the product R&amp;amp;D team can improve and remedy them.&lt;/p>
&lt;p>So the purpose of software testing work is: &lt;strong>to assess the quality status of the object under test as timely and accurately as possible&lt;/strong>&lt;/p>
&lt;p>My other post &lt;a class="link" href="https://chengxiaqiucao.github.io/post/07-%E5%88%B0%E5%BA%95%E4%BB%80%E4%B9%88%E6%98%AF%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E7%9B%AE%E7%9A%84/" target="_blank" rel="noopener"
>The Real Purpose of Software Testing&lt;/a> explains this point in detail, so I will not repeat it here.&lt;/p>
&lt;p>Judging from the purpose and value of the software testing profession, this role is not a production unit but a support unit. Through the various testing techniques associated with the position, it protects the product and keeps it from suffering losses due to quality problems.&lt;/p>
&lt;p>Therefore, as long as quality remains a core attribute of a product and quality problems can affect whether a product succeeds, the testing function will remain a necessary technical branch and a function that must be included in software product R&amp;amp;D.&lt;/p>
&lt;h2 id="skill-requirements-for-software-testing">Skill Requirements for Software Testing
&lt;/h2>&lt;p>Since software testing is a technical role, doing this job well cannot be separated from mastering a variety of related skills.&lt;/p>
&lt;h3 id="foundational-skills">Foundational Skills
&lt;/h3>&lt;ol>
&lt;li>First, knowledge related to the software development process and the operation of software projects themselves. Understand the complete process of software engineering from requirements to delivery, and understand project operations and the role of the testing position within them. What exactly is the software development lifecycle SDLC? What is the testing lifecycle? The relationship between traditional development models and Agile development? What activities does Agile involve, and so on?&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010_hu_719eb94870755e45.webp"
width="1024"
height="628"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010_hu_52adc549d10cac9b.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010_hu_719eb94870755e45.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="163"
data-flex-basis="391px"
>
&lt;/p>
&lt;ol start="2">
&lt;li>Mastery of basic testing theory, mainly the various testing methods and testing types, and an understanding of various testing concepts&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-1_hu_14c0f0842932678a.webp"
width="1024"
height="1215"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-1_hu_4d4ee478d5b91285.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-1_hu_14c0f0842932678a.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="84"
data-flex-basis="202px"
>
&lt;/p>
&lt;ol start="3">
&lt;li>
&lt;p>Skill requirements related to testing work itself. Including the writing of test cases and test reports, the requirements for submitting Bugs, fault severity standards, fault handling processes, and status reports&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Requirements for business understanding. The components of software requirements, the relationship between overall product architecture and requirements, the relationship between product software design and functions, etc. You need to build up an understanding of the product and its business logic.&lt;/p>
&lt;/li>
&lt;/ol>
&lt;p>With the foundational skills above, you have basically met the basic requirements for completing testing work.&lt;/p>
&lt;h3 id="technical-capabilities">Technical Capabilities
&lt;/h3>&lt;p>Beyond mastering foundational skills, doing testing work well inevitably requires mastering further, more advanced related knowledge.&lt;/p>
&lt;ol>
&lt;li>Related IT skills. Mainly the major areas of operating systems, databases, and networks. Each of these areas has enough depth and breadth. Few people can be extremely proficient in every direction. But to grow into an excellent tester, these capabilities are indispensable.&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-2_hu_f3e1333025e09a84.webp"
width="1024"
height="1276"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-2_hu_4e91038153898100.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-2_hu_f3e1333025e09a84.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="80"
data-flex-basis="192px"
>
&lt;/p>
&lt;ol start="2">
&lt;li>Some advanced testing types—testing types that need to be built on a higher technical capability foundation—mainly performance testing, security testing, and some specialized testing&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-3_hu_df4bcf45f9402535.webp"
width="1024"
height="584"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-3_hu_9b4bde9f738d7501.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-3_hu_df4bcf45f9402535.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="175"
data-flex-basis="420px"
>
&lt;/p>
&lt;ol start="3">
&lt;li>Skills related to test automation. Being able to implement automation is already a must-have skill for testers today. Automation capability is built on programming ability and tools for different automation types.&lt;/li>
&lt;/ol>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-4_hu_4439dec09d1fecae.webp"
width="1024"
height="1242"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-4_hu_43e82974ff73365a.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-4_hu_4439dec09d1fecae.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="82"
data-flex-basis="197px"
>
&lt;/p>
&lt;h3 id="soft-skills">Soft Skills
&lt;/h3>&lt;p>Software testing is also a role that places great emphasis on collaboration and communication skills. Therefore, beyond technical capabilities, certain related soft skills are especially critical to whether you can do this job well and do it beautifully.&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Testing is not equivalent to checking. A very important part of testing ability also includes soft skills such as reasoning, questioning, and observation. Being careful, spotting clues, and having an inquisitive spirit are especially important for testing work.
&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/testing-checking_hu_dd929c89bdafaa47.webp"
width="1024"
height="782"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/testing-checking_hu_49031c7ebfaab54e.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/testing-checking_hu_dd929c89bdafaa47.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="130"
data-flex-basis="314px"
>
&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Summarization and written expression skills. Producing fault descriptions, test reports, and so on are all expressions of summarization and writing skills. The purpose of testing work is to be able to assess the quality status of a product, and presenting that assessed status is exactly where the written expression skills here come in.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Collaboration and communication skills.&lt;/p>
&lt;/li>
&lt;/ol>
&lt;p>Because of the nature of the work, testing requires frequent communication and collaboration with BAs, with developers, and with other project members, clarifying problems, and often needing to persuade others to understand the impact of a problem on quality. So good collaboration and communication are also an important part of a test engineer&amp;rsquo;s capabilities.&lt;/p>
&lt;ol start="4">
&lt;li>Presentation and demonstration skills&lt;/li>
&lt;/ol>
&lt;p>As the last inspection step before a product is released, testing often has to take on the responsibility of introducing and demonstrating product functions to others during delivery to users or during demo sessions in Agile teams. In such cases, your presentation and demonstration skills are a capability that provides value not only to yourself but also to the team.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-5_hu_1124eea403186044.webp"
width="1024"
height="557"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-5_hu_5073f79438639573.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/Pasted-20241010-5_hu_1124eea403186044.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="183"
data-flex-basis="440px"
>
&lt;/p>
&lt;h2 id="career-development-paths">Career Development Paths
&lt;/h2>&lt;p>For those working in the testing industry, there are generally three directions for personal career development. There is a testing career roadmap online that actually illustrates the growth path of testing quite clearly.&lt;/p>
&lt;p>&lt;img src="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/TestingCareer_hu_2348095a270730f8.webp"
width="1024"
height="539"
srcset="https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/TestingCareer_hu_bfd9c0735d3ca5b8.webp 480w, https://chengxiaqiucao.github.io/post/035-%E8%BD%AF%E4%BB%B6%E6%B5%8B%E8%AF%95%E7%9A%84%E8%81%8C%E4%B8%9A%E5%8F%91%E5%B1%95%E5%89%8D%E6%99%AF/TestingCareer_hu_2348095a270730f8.webp 1024w"
loading="lazy"
class="gallery-image"
data-flex-grow="189"
data-flex-basis="455px"
>
&lt;/p>
&lt;ol>
&lt;li>The management track&lt;/li>
&lt;/ol>
&lt;p>This line is actually the main one. Under China&amp;rsquo;s specific conditions, once experience, technology, and seniority reach a certain level, people still gradually transition toward management, climbing step by step from test lead, test manager, and test director to quality director and vice president along such a line.&lt;/p>
&lt;ol start="2">
&lt;li>
&lt;p>The technical track
And as a technical role, most companies do in fact provide a technical development channel, achieving career development through technical advancement—from mid-level and senior engineer to staff engineer and even expert engineer, through the software technology track.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>The business track
In addition, as the role in an R&amp;amp;D team that is relatively more familiar with the overall business, testing moving toward the business track is also an important growth channel—from test analysis to business analysis and even to roles such as project management and QA—likewise a suitable development direction.&lt;/p>
&lt;/li>
&lt;/ol>
&lt;h2 id="future-prospects">Future Prospects
&lt;/h2>&lt;p>Finally, let me talk about the worries many students, including quite a few fellow testing practitioners, have about the prospects of the software testing profession: Is testing already in decline? Is the future direction of development the gradual elimination of testing?&lt;/p>
&lt;h3 id="is-traditional-development-obsolete-and-does-agile-development-not-need-testing">Is Traditional Development Obsolete, and Does Agile Development Not Need Testing?
&lt;/h3>&lt;p>Actually, a few years ago there was already a wave of opinion that testing positions could be gradually eliminated. &amp;ldquo;Google and Facebook disbanded their testing teams,&amp;rdquo; &amp;ldquo;the ratio of developers to testers shrank to 10:1,&amp;rdquo; and the rise of Agile development, which defines only a single development team—all of it seemed to suggest that testing is no longer a necessary role in the modern software development process.&lt;/p>
&lt;p>In fact, Agile development does not weaken testing; on the contrary, it emphasizes testing even more, especially shift-left testing. Practices such as TDD (test-driven development) and requirements acceptance criteria all emphasize the importance of functional testing. It is just that these practices place testing more inside the development team rather than in a separate, dedicated testing team. Agile no longer distinguishes different roles within the Agile team (dev team), but instead emphasizes that the team should possess the various roles and capabilities needed to complete product development.&lt;/p>
&lt;p>In other words, although Agile defines only three roles—PO, Scrum Master, and Dev Team—the Dev team should in fact contain members with a variety of capabilities, including designers, developers, and testers, without subdividing specific responsibilities, emphasizing the team as a whole, and it is possible that some members wear multiple hats.&lt;/p>
&lt;p>So it is not that Agile rejects testing, but that it treats R&amp;amp;D activities, including testing, as a whole. We could just as well say that in Agile there is no longer design, no longer configuration management, and so on.&lt;/p>
&lt;h4 id="dedicated-testing-roles">Dedicated Testing Roles?
&lt;/h4>&lt;p>So does this change mean that dedicated tester positions will disappear?
Judging from the definition of Agile, that is indeed the case. Just as in Agile there would no longer be dedicated design personnel, configuration personnel, or even a definition of developer roles. In this sense, there are no longer specialized test engineers in Agile teams.&lt;/p>
&lt;p>But on the other hand, as I have discussed in other articles, Agile emphasizes the team as a whole, with the whole being responsible for quality and the team self-organizing to complete all aspects of product development. This is the ideal of the group of software development masters who proposed the concept of Agile, but an ideal is not the same as reality.&lt;/p>
&lt;p>The reality is that each trade has its own specialization, and in particular the two functions of development and testing are inherently somewhat opposed to each other.&lt;/p>
&lt;ul>
&lt;li>Developers tend to pursue certainty. Based on certain requirements and steps, they define the product&amp;rsquo;s behavior.&lt;/li>
&lt;li>Testers, by contrast, need to consider all kinds of possible paths and branch scenarios based on uncertainty, and to assess the product&amp;rsquo;s possible behavior based on the unknown.&lt;/li>
&lt;/ul>
&lt;p>The opposition between these two ways of thinking determines that it is hard for one role to do both development and testing well. In Agile teams, there will still be a need for roles that lean more toward testing. Dedicated testers will inevitably continue to bring their professional value to bear.&lt;/p>
&lt;h4 id="the-transformation-of-testers-themselves">The Transformation of Testers Themselves
&lt;/h4>&lt;p>Of course, the emergence of Agile has also provided an opportunity for testers to correct some previously mistaken values. Testing is not for finding Bugs, nor is it merely for verifying requirements. Rather, from the perspective of product quality, it assesses the quality status of the product, with the goal still being the realization of the product&amp;rsquo;s own value. Testing should take on part of the QA function within an Agile team.&lt;/p>
&lt;h3 id="will-test-automation--ai-replace-testing-roles">Will Test Automation / AI Replace Testing Roles?
&lt;/h3>&lt;p>Another major worry is whether, with the development of AI, testing positions will be replaced by AI. Of course, this is not limited to testing; other IT roles, including developers, have similar concerns.&lt;/p>
&lt;p>Frankly speaking, given the current pace of AI development, it is hard to say whether, ten years from now, something like programming or software development will still be a profession that relies heavily on strong skills. Developing products may be more about accurately describing your ideas to AI, with AI completing the implementation based on the input requirements.&lt;/p>
&lt;p>In theory, testing roles are similar. Many mistakes that programmers would originally make are inherently avoided by AI when it implements things, so bugs in the programs themselves will be greatly reduced. But beyond that, part of testing work consists of test scenarios that were not considered. Of course, AI can supplement many exceptional scenarios on its own based on requirements, but if a scenario is strongly business-related, AI may still find it difficult to fully cover it through its own reasoning.&lt;/p>
&lt;p>In addition, many exceptional test scenarios depend heavily on the construction of the test environment, and simulating these exceptional situations—such as network disconnection, insufficient resources, and high concurrency—should still be rather difficult without the intervention of an actual operator.&lt;/p>
&lt;p>There is one more point: the training of AI itself also has the problem of data poisoning. Just as automated testing today also has the problem of Bugs in the test scripts themselves, verifying the effectiveness of AI itself also falls within the scope of testing.&lt;/p>
&lt;p>So from these perspectives, AI cannot replace testing work in the near term.&lt;/p></description></item></channel></rss>