The project experience of resume and several problems that testers should pay attention to in writing

Hello, everyone , I'm Daejeon .

Today, I'd like to summarize some problems that testers should pay attention to when writing the project experience in their resumes ：

1、 Projects in progress , Reflect the project time cycle

For example, what you do within two years or six months ** project .

2、 Adjust the order of responsibilities ： At the top is the main responsibility

If you are the test leader / Ordinary QA What benefits and values will be generated ： Such as quality （ The delivery quality becomes better ） And efficiency （ The test efficiency is high after the introduction of automation , The test cycle is short ）, You can also present your own submission bug The situation of 、 How about the delivery quality . Solve problems based on Problems and pain points , People used to measure it very slowly , How to solve , Take the data to prove , Shorten to 40% wait .

The test leader can also write ： Take some students to do the project , How to cooperate with others 、 How to take it with you 、 How to divide the work 、 Test one's own work with quality and efficiency , If you prefer the person in charge, there is also a hidden job, that is, what is the training of talents , such as ： Brought a few people with relatively little experience , To what extent can we achieve from the beginning , What can be achieved in the end , In addition to their own efforts , And how we teach and so on .

3、 Interface / Automated measurement

How to calculate the interface coverage , How many interfaces are there in total , Automated regression , How interface automation is layered , How many single interfaces , How many mixed scenes , What is the success rate of the operation , If there is a failure , What are the biggest reasons for failure , These questions should be clearly thought out by yourself .

4、 About efficiency tools

Test data construction and preparation , By writing a tool to construct , The time for a single transaction has been reduced from how much to how much , How much it used to be, how much it is now .

5、 For project results

on-line bug Less , How much has been raised in the past two years bug, For the phased achievements of these two years , Leakage rate , The logic is clear , No, bug, There is no difficulty in not calling , It could be a function  bug less , The difficulty of version testing lies in compatibility （ Explain the information of each dimension clearly ： Business characteristics 、 Pain points 、 compatible 、 Safety, etc ）

6、 Check key words

Be consistent with your own explanation , The figures in the project need to be very clear , Benefit data need to be sorted out .

7、 replay

One side didn't answer well , Continue to use search engines to check , Make a second round . Because two sides and three sides are very likely to continue to ask .