What if the test engineer has no status in the team?

Why is there such a problem

First of all, self-examination, why the position of oneself & the organization in the team is not so high, and the influence is not so great. In a project team, every role is indispensable. If a certain role has a low status and is not trusted, then this role will have to check itself.

From the perspective of testing, if a development student often makes mistakes, the developed program has a high bug rate, and the bug is fixed over and over again, then the development student will have a bad impression of the test and may even be pulled by you. Into the blacklist, you will be extra careful when encountering his projects.

From the perspective of a developer, if a tester often misses tests, raises bugs for the same type of problem multiple times, raises multiple bugs for the same reason, and other low-level mistakes, then the tester will not have a good impression of the developer .

Secondly, self-examination, whether what we do is beneficial to others and the team, whether it is convenient for teammates or has caused trouble to teammates.

What if the test engineer has no status in the team?

How does what we do help the team

Here is an example to illustrate:

The Spring Festival is approaching, and the WeChat red envelope function is about to usher in another peak period. Take the example of scanning codes to receive red envelopes.

1. How will you test after you get this requirement?

2. How to conduct scalability test?

Ordinary test engineer:

1. The action of distributing red envelopes: refilling money in red envelopes (interacting with the cash register), there is a lot of mystery in this action. For example, the balance in the wallet is insufficient, the balance in the bank card is insufficient, the limit is exceeded, the maximum limit of the red envelope is exceeded, how to charge the handling fee (if any), and under what conditions can the red envelope be issued, etc.

2. Generate QR codes: how to generate QR codes normally, how to deal with failed QR code generation, how to deal with the clarity of successfully generated QR codes, and how to deal with weak networks.

3. The action of receiving the red envelope: how to identify the identity of the recipient, how to recognize that the red envelope has been received, how to deal with the red envelope not received, and the logic of the red envelope.

Interface Test Engineer:

1. Can the interface layer bypass the quota?

2. How to deal with the interface cache, how to deal with the cache invalidation, and how to deal with the first request.

3. How to deal with interface concurrency, and whether the amount of the red envelope received exceeds the amount of the red envelope itself.

4. How to control interface permissions (network security)?

5. How is the interface encrypted? Is there any sensitive data returned in plaintext (network security)?

Performance Test Engineer:

1. There are many people sending red envelopes at the same time, how many qps can the generation of the QR code carry?

2. How to ensure that the QR codes will not be generated at the same time and cause duplication?

3. There are so many people receiving red envelopes at the same time, and only 5 people can receive one red envelope. How can we ensure that these 5 people can receive the red envelope successfully and others cannot. How much qps can be carried by the action of receiving red envelopes, whether it can meet the business peak demand, and whether rapid expansion can be solved.

Digging a little deeper:

1. The interface is abnormal, how to track the log, how to see the direction of the data flow, and which link is wrong. When you help the development students locate the bug, or the approximate scope, the development students will thank you.

2. If the interface relies on a third party, how to quickly switch to the backup channel if there is a problem with the third party.

The above is a simple example, listing some test directions, and there are still many details that have not been fully considered. Welcome to leave a message to discuss.

If you just do the work of an ordinary test engineer, even if you do a good job, when the test environment is tested, there seems to be no problem in function, and various problems will be exposed as soon as it goes online. For example, red envelopes cannot be sent out during peak hours; too many people grab a red envelope at the same time, and the amount of the red envelope cannot be matched; the program is wrong, and the problem cannot be quickly located (there are very few useful logs), etc. The development students will also be very tired to fix bugs urgently because of the problems of this project, and they have to start the work of the next project. At this time, he may be detonated with a single sentence. Subsequent cooperation will also feel that the value of testing classmates is not high enough.

What kind of partners and teammates does the team need?

You must know that in the team, everyone's interests are tied together. Only by mutual benefit and win-win can we cooperate with each other for a long time and trust each other more. As long as you can help your teammates solve problems while completing the work and make them feel comfortable and at ease working with you, then your influence with your teammates and even with the team will naturally increase.

take stock of yourself

In our career, different time periods require different knowledge and experience, and different stages have different requirements for us.

Take stock of yourself every once in a while, recognize the present, recognize yourself, and don't be trapped by your comfort zone.

When your talent can't support your dream, go to recharge.

When you can't achieve your goal after doing one thing for a long time, try to change your way of life, try to be altruistic, only true altruism, in return for him, maybe you will have unexpected gains.

I always believe that everything in this world is balanced. If you want to get something, you must pay something. If you lose something, you will gain something in another place.

Plan your own direction for charging

After taking an inventory of yourself, you will find some unexpected gains and some shortcomings. Inventory in different time periods, you will be surprised to find that each inventory will be different.

If charging is planned, the efficiency will be much higher.

In the era of such a developed network, online videos and various courses can teach us a lot. But if we want to carry out cognition systematically, it is recommended to read books. Books can allow us to see more comprehensively and form our own knowledge system.

Practical case

Optical theory is useless, you have to learn to follow along, and you have to do it yourself, so that you can apply what you have learned to practice. At this time, you can learn from some actual combat cases.

If it is helpful to you, please like and collect it to give the author an encouragement. It is also convenient for you to quickly find it next time.

If you don’t understand, please consult the small card below. The blogger also hopes to learn and progress with like-minded testers

At the right age, choose the right position, and try to give full play to your own advantages.

My road of automated test development is inseparable from the plan of each stage along the way, because I like planning and summarizing,

Test and develop video tutorials, study notes and receive portals! ! !

Guess you like

Origin blog.csdn.net/m0_59868866/article/details/132699046