I am coming again. Because this job is so idle now, I go to work for 8 hours, fish for 5 hours, and now I am going to get off work again, turn off the phone, and get my salary in one day, which is boring and refreshing.
I understand now that the company recruited me, maybe it was just for fishing full-time, right?
As I mentioned in a previous article, after more than a year of suffering and choices, I finally successfully changed jobs in May this year. The salary doubled, the work was easy, weekends, away from overtime, and I was able to catch fish by the way.
After I got the new offer, I knew that the new company was much better than the previous one, but what really made me understand the feeling of being so boring and wanting to quit was that I had nothing to do after joining the job, never worked overtime, and the workload was pitifully small .
I even wondered for a while, why did the company spend such a large cost to recruit a person? I recruited and did not arrange reasonable work for them. My daily work now is to turn on the phone, open DingTalk, open Zen Road, test the APP, chat with the developer, and close the BUG after the test. Open the background every day and pretend to look at it a few times. In fact, there is nothing to test. They are all very simple bugs. According to the agile iterative testing ability I practiced in the last company, other colleagues may need to test these pediatric bugs. One day, I did it in two hours.
Remarks: My previous company was working on an e-commerce system, with one iteration every two weeks, and one or two small iterations in between, so it is a typical agile iteration, 8 hours are used as 10 hours, and it is often to test a BUG I have to look at the next BUG immediately, and even the development will interrupt me and let me test the other one first. Although it is very troublesome, there is no way. Small companies are like this, not to mention that I am alone in charge of the entire e-commerce platform. The test, so these things can only be resisted by me.
Although this company is also an Internet company, it is very idle. Many products have entered the operation and maintenance stage, and each iteration is just doing some repairs, and at most it is adding a few small requirements.
The reason why I accepted this offer at the beginning was that I had stayed in the previous company for two years and it was time to run away, and the second was that I was too tired and the salary was low, only 7K, so I had to change jobs and increase my salary. After accepting the new offer, I originally wanted to show my strengths in the new company. I have taught myself jmeter interface automation, python automation, performance stress testing, monitoring, etc. in the past year, and I also thought about using the new company's projects Build an automation framework and use it to practice, but now the leaders don't pay much attention to it, and the related projects are relatively simple, so there is really no need to automate.
So the wish came true...
Anyway, my current daily workflow is like this:
8:25 to the company,
Turn on the phone and start a day of fishing,
Test a few bugs,
In the afternoon, visit CSDN, blog garden, or github to see if there are any good open source projects.
Like me today, I developed and repaired several BUGs in the APP. I simply tested it and fed back the results to the group. Look at Docker, k8s, redis, mysql performance optimization and more.
Learn more about the dry goods knowledge of the great gods.
Then at 5:50, I went to the bathroom, and at 5:59, I turned off the phone, and I got my wages for the day again, hahaha.
What a fulfilling and enjoyable day.
However, according to my personality and career planning, this company is about to resign soon.
Sometimes I run away because I am too tired and my salary is too low, such as when I went to a company; but sometimes it is because it is too easy and there is no room for improvement, especially for companies that follow the steps and have no opportunity to learn. I originally taught myself Quite a lot.
There is no shortage of jmeter interface automation, performance pressure testing, python automation, etc. I think I can play in the new company, use the company's projects to practice, and then improve, but I didn't expect the new company to have no chance for me to practice. Can't make me stress test...
Too depressed, so I had to slip away. Another point is that when I accepted the offer from this company, it was actually temporary. First, I raised my salary to a higher level, such as 7K to 14K. Then the next job can be based on 14K, and I mentioned 18. Preferably 20.
The day before yesterday, because of the company's operation and maintenance, the test server had to be shut down, so we can only test in the development environment, ah, it's so annoying.
The development environment is very messy. I opened the background of the project and reported an error after clicking a few pages. I feel that the development environment is just merging codes and publishing them. There are bugs everywhere. I also encountered this situation in the previous company, because there were too many requirements for a while, and we iterated agilely, iterating once every two weeks, so I didn’t test in the test environment during that time, it was directly Tested in the development environment, although the test speed is faster, but the quality is hard to say, there are always inexplicable errors and various problems, because each of their development has the authority to merge the code into the development environment, so sometimes the code is written in a pile BUG, I still posted it, which made my head big and my work was useless. I didn't expect this company to do the same now. Hey, it's hard to say.
One more thing, the BUG of the small program I mentioned last week, the female colleague at the front end has not been fixed, it has been delayed for a week, and then today I was bored, I clicked on the Zen Tao, and I found that the female colleague logged in for the last time Zen Tao was last Friday, that is to say, this week, she didn't even read the BUG I mentioned... and she didn't know what she was busy with.
So this incident tells us that after testing and raising bugs, we must notify relevant developers in a timely manner. Some people are very conscious and check whether there are new bugs assigned to them on Zen Tao every day, but some developers do not have this self-consciousness. Yes, just like the female colleague just now, in the end I couldn’t help sending her a message to let her see, remember to fix the BUG......
As a tester, I would like to share my summary of technology over the years, and a set of learning routes, hoping to help friends who are determined to go all the way on the road of technology!
"Software Test Engineer Development Planning Route"
1. Test basis
Understand the basic skills of testing, master the use of mainstream defect management tools, and be proficient in the operation and maintenance of test environments
2. Necessary knowledge of Linux
As the most popular software environment system, Linux must be mastered. The current recruitment requirements require Linux ability
3. Shell script
Master Shell script: including Shell basics and application, Shell logic control, Shell logic function
4. Principles of Internet Programs
The only way to automate: the basic knowledge of front-end development and the necessary knowledge of the Internet network 4. Principles of Internet programs
5. MySQL database
Software test engineers must have MySQL database knowledge, not just the basic "addition, deletion, modification and query".
6. Packet capture tool
Fiddler, Wireshark, Sniffer, Tcpdump and various packet capture tools are suitable for various projects, there is always one that suits you
7. Interface testing tools
Interface testing artifact, a powerful tool you can't avoid: Jmeter. Small and flexible: Postman
8. Web automated testing
Java&Python understands the purpose of automation, proficiency in TestNG&unittest automation framework, as well as assertion and log processing
9. Interface and mobile terminal automation
Professional interface calling and testing solutions. Build a complete web and interface automation framework, and use Appium as a whole
10. Agile testing & TestOps construction
Unveiling the mystery of TestOps, continuous integration of the Jenkins framework is familiar
11. Performance Test & Security Test
The other side of software testing: performance testing and security testing, choose a direction and work hard to climb the pit!
Complete the construction of such a system. It can be said that this process will make you miserable, but as long as you get through it. Later life will be much easier. As the saying goes, everything is difficult at the beginning, as long as you take the first step, you are already halfway to success. The ancients said, "If you don't accumulate steps, you can't reach a thousand miles." When you look back on this journey after completion, you will definitely be moved. a lot. It's easy to complete half of the monthly salary of more than 10,000
I believe that you will continue to explore and improve according to this learning framework route, and break through the bottleneck of technology. It can be said that this process will make you miserable, but as long as you get through it. Later life will be much easier. As the saying goes, everything is difficult at the beginning, as long as you take the first step, you have already succeeded in half, and when you look back on this journey after completion, you will definitely feel a lot of emotion. I have also gone through such a journey before I can get more opportunities for high-paying positions. The hard work will eventually pay off, which can be regarded as a recognition of my ability and a real proof of my own value.
Finally: [Video tutorials that may help you]
Finally, I would like to thank everyone who reads my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it
