Graduated with a small break, no skills and no connections. I am ignorant and understand how to embark on the road of testing, and I have graduated for more than two years. When I'm bored, I write down my own soft test path. Reference: https://www.cnblogs.com/Chilam007/p/6092971.html#3567691 It is exactly the same as my experience
First internship company (April-August 2018)
At that time, I just came out to look for a job, and I was in a state of confusion. When I posted my resume online, I just came out of society and didn’t have any work experience plus a little undergraduate degree. So I bumped into walls during the interview. I have forgotten how many companies I had interviewed at that time. It should be only three or four, I asked. Sometimes I can’t answer the question, sometimes I’m still thinking about it for a while before answering...Finally, I joined the company hastily for two reasons: 1. The classmates are in it; 2. The salary of the company. It's pretty high for interns. In general, the vision was too short-sighted.
This company is a router, research and development + production. I have been in this company for less than half a year, and my work is to maintain a project developed by a colleague. When I entered, no one took it at all. The boss threw me a project and asked another colleague to help me deploy the environment, and then let me take a look at the project first, and watched that one or two months passed. I still don't understand what my job responsibilities are. I still go to get off work every day, daze at the computer or talk to others, sometimes I dare not leave work on time, because my colleagues in the office leave only half an hour late.
Later, I finally came alive~ Let me contact the sales colleagues in the branch, probably adding a query or search function according to the needs of the customer, or adjusting the UI to fix the BUG found by the customer. Only then did I realize, yeah, this is work.
Gradually, the company's requirements became more and more difficult for me, so that a function would have to be delayed for more than half a month. Finally, under pressure, I had to resign. I feel that my technology is not up to the development work, and many of them are solved with the help of colleagues.
At that time, I was a little dizzy, thinking that I could get my salary every month without having to work. In the end, I realized that I didn't know what the test was about, and I didn't understand it. After a few months, I thought I could bite the bullet and do development. In the end, I realized that it was nothing. The boss often comes to care about how I'm doing. My first company internship trip is over. After almost half a year of soy sauce, there is no growth. Realizing that I belong to the doctrine of taking, when I ask for help, I don't think about why this can solve this problem. What is the principle? Anyway, I blessed that everything would be fine if I could solve it, and I also realized that I was passive, and I never took the initiative to look for things, or took the initiative to ask others about problems. In the final analysis, I just entered the workplace and I was too courageous.
The second company (October 18-20 April)
This company was found after barely resigning. It seems that there are not many interviews this time. Some companies have sent interview invitations, but because of offers, they all declined one by one. (The only thing that is better than the previous company is this position. It's a real test position (two lines of tears in my heart), and there are five insurances + weekends, the company seems to be pretty good in all aspects of the environment (the specific brain is flooded).
The company is doing notebook outsourcing testing. There are dozens of people in the test product center. Each person is responsible for different modules. I am responsible for the functional testing of the multi-language system and its own desktop program. I'm getting started soon, and I'm basically familiar with the business process of the system.
Here is an introduction to the working mode of the R&D team:
1. After the tester finds a problem in the test system, he raises the BUG to CASEDB;
2. After the development is confirmed to be a BUG, the code will be checked in to the DB after the repair is completed, and the relevant document must be checked in, that is, there is a description document to describe which problem the checked-in code solves, and if it is not a BUG, it will be closed directly;
3. Test colleagues for packaging work (use the packaging tool independently developed by the company to package, that is, get the latest DLL or script checked in by the development and put it into the corresponding full version folder);
4. After the packaging is completed, the tester takes the program script to update to the local, and then starts the test work. After the test passes, fill in the result (OK or NO) in the description document and modify the status of the BUG on TFS. If it fails, contact the development Communicate and see if the code is not fully checked in (this happens often, either the script is missing or the code is missing), or there is a problem with packaging (there are many problems with packaging tools, and there are often BUGs), or the problem itself Not completely repaired;
The above is the working mode of the team. The company’s software system is iterated very frequently. It is regularly upgraded once a week, and a major version is issued once a month. This is not even counted as other projects that are intermittently inserted, so the R&D team It's a word, busy! !
Well, in fact, this model will be used for almost a year in the future. It feels a bit like a factory assembly line. There is no extra time to learn. However, after the new boss replaced the original boss, many parts of the department are slowly improving and learning. Some basic skills to be mastered for testing, such as writing test cases, how to use the scenario method to carry out testing, and the test summary after the project ends, all of which can be regarded as an improvement of skills.
In fact, logically speaking, I should be grateful to the company for giving me this opportunity for me to learn a lot, and I should continue to fight with the company, but I am too jealous and follow the trend.
At the end of the year, there were at least 4 people in the department preparing to change jobs. Being smart, I thought that I hoped to raise the processing capital after they were almost gone, but I didn’t expect that I was still too tender, and I felt that I worked hard. For a long time, I worked hard all day to work overtime for the project, but the boss’s focus was not me, and I was inevitably lost. Anyway, combining many factors, I found many reasons for myself to leave, and finally ended the work of the second company.
The third company (April 20-present)
I have to say that I just graduated, my heart is still too impetuous, so in just over a year, this is my third company. Several other colleagues jumped at double and doubled jobs, but I followed suit with hundreds of hundreds of jumps. It was a failure. There are several reasons: 1. The wage level in the computer software industry is not too high; 2. Many companies are disgusted with people who frequently change jobs; 3. Their own abilities are not bad and their skills are insufficient.
The work content of this company is actually the same as that of the second company. It is all functional testing, with no access to performance, and there are few projects. It is on time to get off work every day, which does not create a decadent self.....
I have been here for more than half a year. In terms of skills, it can be said that I have not learned at all. The boss never thinks of how to improve our skills. It is completely irrelevant, as long as the system functions are run through. On the contrary, when I first came in, I learned some experience of being a person and doing things with the team leader. Whether it is big or small, you should face it with a positive and optimistic attitude, and you must be patient. Anyway, it is a kind of "the world is full of beautiful things". The mentality is right to work. But the same is true, day after day...