Last week, our company’s performance interviews were all over. At this time of the year, it’s time to focus on performance. For workers in the workplace, performance is definitely one of the most important things. The reason is very simple: bonuses, promotions, salary increases Salary has something to do with it.
For example, the following Meituan employee's self-exposure on Maimai is very bleak:
Everyone on the Internet knows that if the performance is marked C, not only the bonus will basically disappear, but even face optimization and elimination.
Conversely, if the performance is A or S, it means rich rewards and opportunities for salary increase and promotion.
It just so happened that an administrator at the part-time management week meeting today also asked this question: how to achieve high performance in the company.
This is definitely a good question, and it is also a question that is closely related to everyone. Today I would like to share with you some of my suggestions:
1. Clarify the performance requirements of the company and the position
This thing is really different for each company and each position. For example, some companies will look at the length of overtime work, whether they are absent from company cultural activities, etc., and some companies only look at work output.
For technology, it may depend on whether there is a delay, whether the code product is stable, the speed of online bug resolution, etc. For testing, it may depend on the effective bug rate, online failure rate, etc.
Only by clarifying the logic of the company and position for high performance can we move towards high performance in our daily work.
2. Use data thinking to publish weekly work reports
Today, the group management mentioned a problem: Because she is a newcomer, and the company has just started to implement new performance rules, she feels that she will be blamed.
Sending a weekly work report with data thinking can prevent you from being blamed, because your grades and work conditions have been digitized by you, it is easy to appeal, and the leader will naturally weigh it.
Whether all the achievements and reports at work can be turned into data is very important, whether it is technology, products or other positions, it is the same.
For development, how long did it take you to develop this feature, and was it faster than others? After going online, what are the technical indicators such as stability, access speed, and crash rate?
For the product, what impact did you make on which user indicator did this product function have? Is the retention increased or the number of activities increased?
For operations, what is the impact on GMV after this campaign goes live, what is the conversion rate, and what is the nps value?
In addition to clearly explaining your grades, the data can also identify problems and find out the next improvement point. Quantifying your work with data as much as possible will allow you to accumulate successful experience, and reporting with data as much as possible will make it easier for leaders to find bright spots.
3. Focus and refocus
Always have a clear goal in your work, and at the same time keep focusing on the goal, so that you can produce good work results.
Only the goal is not enough, you must learn to review the review on a weekly basis, and quickly re-enact once you find that you have deviated. Using OKR management tools to manage yourself is very reliable and effective.
4. Keep deadLine in mind
Procrastination is a problem that many people have. It is human nature and it is difficult to completely overcome it. This caused many people to touch the fish first after receiving the task, and finally sprinted all night, and the result was not necessarily good.
Here is a little trick: disassemble the task, turn a large cut-off point into many small nodes, and set a dealline for each small node.
In this way, you can always work efficiently around delivery. The project manager's set of task dismantling is actually suitable for everyone.
A big task will always be clueless, and after dismantling, it can be completed one by one on schedule to control the risk of delay.
5. Upward communication
Many leaders say that they only look at the results and not the process. Please remember that this is nonsense: leaders are also human, and they also have various emotional factors, so upward management in the process is equally important.
Many people have made good grades, but they can't get a salary increase or promotion. Many people have been working as scalpers in the workplace for many years, and many people have been doing repetitive work without growing.
Whom to blame? In addition to lamenting that there is no Bole, you have to review yourself: Have you clarified your demands with the leader? Have you reported your credit clearly?
There are still many students who work very hard and hard, but they always fail to do well in the things assigned by the leaders. This requires reflection on whether they have clarified their expectations with the leaders when taking on tasks?
In particular, it is recommended that after receiving an oral task, you must understand and reconfirm with the leader.
Risks and deviations found in the process of work execution must be reported in a timely manner. Don't take chances and wait for feedback until it is out of control.
Upward management also requires learning to fight for resources. It is said that crying children have milk, which is indeed the case. The company's resources are limited, if you can't get it, it must be cool.
Except for some notices, work ability is the biggest and most obvious aspect that you can feed back to the company, and all work ability is the one that has the greatest relationship with your performance.
As a tester, I would like to share some of my generalizations and conclusions about technology over the years, and share my notes on the skills that an advanced automated tester needs to master. I hope it can help those who are interested in technology. Friends all the way to the end!
Junior software test engineer professional skills reserve
1) Understand the basics of computer and software testing
a. Basic computer knowledge
Computer components, operating system classification, common system architecture (B/S and C/S), commonly used DOS commands
b. Basic theoretical knowledge of software testing
The purpose, definition, principle of software testing, product quality model, basic process of software testing
2) Commonly used Linux commands
In software testing, sometimes we need to build the test environment by ourselves, or deploy automation projects on the server. The servers basically use the Linux system, so we need to master some basic Linux commands
3) SQL statements
In software testing, the verification of test results or the preparation of test data in automation will be done by operating the database. Therefore, for the most basic addition, deletion, modification, and query SQL statements of the database, it is necessary to be able to write independently
4) Writing of manual test cases (most important)
As a software test engineer, the most basic requirement is the ability to write use cases. How to write a test case with high coverage and low repetition rate is the ability that should be constantly pursued when entering the software testing industry.
5) Defect management
Understand how to manage the bugs proposed by testers in the team, so as to ensure that the bugs of the project can be repaired in time. Mastering the
above skills, for a student who is new to the software testing industry, he will definitely be able to gain a firm foothold.
Intermediate software test engineer professional skills reserve
1. Professional skills related to interface testing
Whether it is automated testing or performance testing, or even developing in the direction of test development, the most basic thing is to test the interface. Therefore, if you want to be a good intermediate software test engineer, the first step is to be able to complete the interface test.
1) Basic theoretical knowledge related to interface and interface testing
Including the concept of interface and interface testing, the principle of interface testing, the process of interface testing, http protocol, Restful interface style. These things need to be understood
2) Use of interface tools: Postman and Jmeter
For interface testing, you can use code or tools. Usually, interface testing is done using tools at most. There is no other reason, "efficient".
3) Packet capture tools: Fiddler and Charles
During the test, in order to locate the front-end and back-end problems, we will use the packet capture tool to view the results returned by the interface. In order to locate the problem is the front-end, or the back-end.
These two tools, we generally choose one of the two to learn, because their functions are the same.
2. Programming language learning
The implementation of automated testing mainly relies on code to complete. So to be able to automate testing, you first need to master a programming language. Currently, the mainstream automated testing programming languages in the industry are python and java. I personally recommend python, because for newcomers, it is less difficult to get started. If you can study all day, you can get started with python in about 10 days
3. Automated testing and learning
After learning Python, we can start learning about automated testing.
The purpose of automated testing is mainly to reduce the time for regression testing.
Automated testing in software testing is divided into UI automation and interface automation.
After passing the above study, let's see what abilities you have?
SQL statements, Linux common commands
Manual test case writing and defect management
Use packet capture tools to locate front-end and back-end problems
Use Postman or Jmeter for interface testing
Use Python for interface/UI automation testing
Knowledge points that senior test engineers need to master
At this stage, you need to broaden your knowledge system, and at the same time have a deeper understanding of the advanced stage, code quality, test architecture, microservices and middleware, containerization, automated test design, test architecture, CI/CD, and shift left testing , test phase, test shifted right.
One of the differences between test development and R&D posts is that R&D pays more attention to depth, while test development pays more attention to breadth.
For example: you need to understand CI/CD, because the test platform/tool you make may need to be connected to the CI/CD pipeline or the operation and maintenance monitoring system
Another example: when you do performance testing, if you don't understand the core knowledge of architecture design, you may encounter many problems that are difficult to solve when doing full-link stress testing and service degradation testing.
In addition to broadening your knowledge system, you also need to refine your coding skills.
That’s all for the above methods of achieving high performance in the workplace. Finally, I wish everyone a satisfactory performance and a satisfactory year-end bonus!
at last
Recently, some software testing learning resources have been sorted out intermittently. The main content includes: testing documents, testing tool installation packages, automated testing video tutorials, performance testing, interface testing, interview skills, resume templates, a full set of interview questions and other knowledge content. The purpose is to learn about the technical hotspots recruited by big factories, and to continuously improve learning
I would like to give you a word to encourage each other: When we are not capable enough, the first thing to do is internal training! When we are strong enough, we can go outside!