I saw an article[1] a few days ago. The title is a bit interesting. I translated it casually and found it to be pertinent overall.
Lust: Overreliance on Technology
Symptoms: Most of your testing activities become "launch this automation", "launch that test pipeline", but most importantly, maintain them.
It's good to want to find the best technology for your project and automate as many tasks as possible. But if you get too stubborn about it, you'll end up with a bunch of code that needs to be maintained. When you have your nose buried in code, you sometimes forget what's most important.
Treatment: Keep the balance: follow good maintenance practices, base your strategy on a testing pyramid... but most importantly, do those damn manual tests!
Greedy: Want to find all the bugs
Symptoms: Your tests take too long, you find a lot of subtle bugs, or some very fringe use cases, and most of the time, they never get fixed.
Trying to find bugs in all new developments is a losing battle. You have to accept the fact that you won't be able to find all bugs, but at least find those that are most likely to be detected.
Furthermore, testing greedily is like testing without method: you'll never improve your testing skills.
Treatment: Force yourself to test for a limited time. This will complete your testing capabilities. Look for the most obvious errors first. If you still have enough time, finally look for some tricky use cases.
Don't worry about undiscovered problems. Trust the process. A good monitoring and user feedback system will allow you to effectively detect bugs that cannot be detected during the normal testing phase.
Rage: blaming an individual
Symptoms: When under pressure, it’s easy to blame the team or individual for writing a big bug. When there is an obvious problem, people tend to point to the person believed to be the culprit.
Remember, this situation is usually the result of a combination of factors: tight deadlines, lack of discipline, missing processes, software that is too complex to maintain, etc. So never blame individuals – it’s outdated and counterproductive.
Therapy: Focus on the problem, not the person. Remember, all mistakes can be viewed as opportunities to improve processes and deliver better results. Learn from it. But also pay attention to communication. Anger often comes from a misalignment between your expectations and reality, so be sure to understand your team's capabilities, keep open lines of communication, and set clear, achievable goals.
Greedy: hoard all testing activities
Symptoms: All tasks related to creating and maintaining tests are limited to one person or a very small team, especially given the size of the entire team.
This results in:
•Bottlenecks in the testing process. •Over-reliance on a small group of people creates risks if any member is unavailable. •People handling these tasks are at increased risk of burnout.
Treatment: Distribute testing responsibilities within the team to gain multiple insights and minimize delays. Promote teamwork and share knowledge to improve the quality of the testing process and final product.
Lazy: ignoring documentation
Symptoms: The team has little understanding of what has been tested. Many features have unclear specifications or no specifications at all. Too few errors are tracked.
Lazy testers only verify written test cases without considering other parts of the testing process, especially documentation.
Without documentation, testing activities can become quite invisible. Simply because documentation is an inherent part of the testing process. You test, observe, and write your observations in a test report. This accomplishes specification, as I like to say: specifying the unspecifiable.
Treatment: Create a test report containing the following sections:
1. Function description: Outline the functions of the test. 2. Test goal: The main goal of the test. 3. Test steps: Repeatable sequential operations. 4. Expected results vs. actual results: predicted results vs. observed results. 5.Bug/Issue: A logged issue, with a reference (if logged). 6. Test environment: software, hardware and network details. 7. Attachments: Links to screenshots, logs, or related files. 8. Comments: Additional tester notes or observations.
Jealousy: Compare with other projects
Symptom: QA team compares itself. Some executives even take it upon themselves to compare the number of bugs found across the company's different products. This can lead to jealousy.
Every project has different challenges and therefore different QA needs. These projects may be at different stages of maturity, they may have different resources, different users, etc.
Treatment: All teams need to understand the context of each project. Celebrate each team's successes, even the small ones, and increase visibility across projects.
Arrogance: Ignoring users
Symptoms: The team is very confident in testing the technology themselves. They were blinded by their own metrics, which proved them right.
Fewer and fewer people know how users use products. Additionally, there is no real user feedback.
This is probably the most dangerous of all sins because it's not always recognized immediately, and when it is, it's often because an obvious bug surfaces and sets off alarm bells.
A: Why didn't you see that bug?
B: I don't understand. All lights are green. We completed all tests successfully.
It's time for a complete transformation of the QA process.
Treatment: Serious mistakes are also the ones from which we learn the most. Adapt to them. Adapt testing to real-life user scenarios. QA must have the functional knowledge required to conduct the most appropriate testing. Hold user tracking meetings. Incorporate user feedback and grow from every experience.
Now it's your turn. Have you ever experienced or encountered any of these sins in your past experiences? How did you overcome them? Leave your comments.
Finally: The complete software testing video tutorial below has been compiled and uploaded. Friends who need it can get it by themselves [guaranteed 100% free]
Software Testing Interview Document
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Alibaba, Tencent, Byte, etc., and some Byte bosses have given authoritative answers. After finishing this set I believe everyone can find a satisfactory job based on the interview information.
