19 Suggestions for improving software testing capability

Original article: cheezburgers and testing advice

Author: Alan myrvold, Senior Software Security Testing Engineer

Note: This article is intended for beginners of software testing, but it is useful for experienced software testing engineers.

At first I prepared to write 10 suggestions for the software tester who just got started. But then I read a speech by Ben huh, a celebrity on LOLcats/icanhascheezburger. Ben pointed out that with the Internet, information becomes free resources, but organization, editing, and expression all require skills. Inspired by Ben and cheezburger websites, I requested 60 successful software test engineers to provide three suggestions for beginners. More than 40 of them replied to me, so that I finally had a list of up to 100 suggestions.

In order to protect their privacy, I will not list these suggestions. But interestingly, I found that there are many areas in common with their suggestions, and all these suggestions add up much better than I previously thought.

I summarized the suggestions I collected into the following 19 items:

1.What customers think

Always think about users during the testing process. Cultivate your own resonance with user needs. Communicate with users and observe how they use your software.

2.Multiple read bug

If you work with a software testing engineer in a team, read the bugs they issue every day, especially those for your testing. You can learn a lot from how others find bugs.

3.Multi-read code

Find the code for the function you are testing. Although writing code is not yours, reading the code will often help you find potential limitations and Software defects.

4.Bugs found for youProud

Fixing a software bug starts with writing the title and description of the bug. Every time I send a bug, I repeat it to make sure it is reasonable and provides details that are just the right benefit. If some important bugs are not corrected, make sure that the decisions and trade-offs are correct.

5.Participate in software function design

Before writing soft code, you can actively participate in the software planning phase when there are still major design changes. This will help you understand the trade-offs and trade-offs that are being considered.

6.Design your test

It is always useful to look for boundary values, use combination technology, draw charts, or create test models to put your ideas into your test design. While testing, you are consciously switching between your testing plan and product learning.

7.Measure the test taker's knowledge about the functions you have tested.

Whether you are testing that feature, you should understand its design, its limitations, bugs discovered by others, code changes, and its interaction with other features.

8.Test your responsibilities with others

Test your functional modules with people of different expertise, discuss the testing ideas, and ask for feedback.

9.Learn the software you tested

Even if you test a small part of a software, becoming an expert in other new features and the entire software will help you become a better test engineer.

10.Cultivate good relationships with developers

Testing work is sometimes adversarial, so that it is easy for some people who work with you to ignore your opinions when making decisions. Establishing a solid relationship with bug fixing developers will be helpful for understanding the latest progress and fixing bugs.

11.Expand your field and network

Successful people all have a solid and trusted social circle. They can get the professional knowledge and suggestions they need. Keep making new friends within your company and developing contacts in the field of expertise.

12.Find a mentor or Role Model

I have worked with many excellent test engineers and learned a lot from them. To improve your testing skills, you should look for "consultants" to meet them or follow their examples.

13.Introspection

Test engineers are good at discovering Software defects. If we apply this kind of sensitivity to ourselves, we will be able to discover our own shortcomings more effectively.

14.Manage your time

Our time is easily occupied by large jobs and constant meetings, so we don't have time to learn, dig more bugs, or even stay healthy. To avoid overdraft, you need to learn how to manage your time.

15.Choose test automation wisely

Automated Testing may lack the "residual vision" of skilled testers ". Incorrect automation sometimes turns into code that is too large to maintain and does not really mean measuring the quality of software. However, well-designed automated testing helps to detect Software defects early.

16.Improve your programming skills

I 've met some talented testers who tend not to write code. This makes sense. Just as movie critics won't consider the likes and dislikes of movie audiences after becoming picky and knowledgeable, when I act as a programmer, I don't want to be the same as a user anymore. But programming is still a valuable skill. It can help you better read the code, understand the inner of the product, and help you write some gadgets to make simple and repetitive work easier.

17.Participate in bug.(Triage)

In the last few days before the product release, the bug Review Group held a meeting to decide which bugs should be fixed and which ones should be left for future versions to fix. If you are not in the invitation list for this meeting, you must take the initiative to ask for participation. You will see a compromise between tester credibility, user impact, known risks, and other factors. This will be a very interesting experience.

18.Continuous learning

Whether it is "soft skills", such as public presentations, programming languages, or new testing technologies, successful testing engineers always take time out of their busy hours to learn.

19.Love what you do and do it well

If you cannot afford to give up your current job, you will learn to love it. Testers sometimes become popular, especially in difficult release cycles. Talents who enjoy their work and are not satisfied with the goals of the plan will become excellent test engineers.

Translator: Huang Jie (software testing and Development Engineer)