When it comes to outsourcing testing, most people's first impression is: high work intensity, low technical content, and no sense of belonging!
I graduated from a non-computer major in an ordinary second-year college, and I took a cross-professional entry test. I have nearly 6 years of work experience so far. The first test job was Huawei's outsourced functional test for 5 years. I also have a general understanding of the main work of outsourcing, and I have some experience. I would like to take this opportunity to share some of my thoughts with you. The overall feeling is:
This job lacks a sense of belonging, and there is always a gap in my heart. There is not much room for improvement, and I
have no access to core technologies. The company does not provide you with technical training and research.
The work is simple and the business is repetitive, usually because of the existence of tool people.
The salary is not high, although there is overtime pay, it is still not high
Whether there is any difference from the employees in the industry, whether there will be discrimination
First of all, in terms of work content, the most outsourced level is generally senior programmers, and there are many architects at the upper level to do technical selection and business analysis, which are generally not your turn to do.
And if it is a daily development task, there is actually not much difference. Generally, which group you are assigned to and what the people in the industry do will be what you will do. The development equipment is the same for everyone, and the computer configuration is different. It will be too high, at the level where you can just develop, but don't want to play games.
However, as an outsourcer, there are indeed restrictions on some operation rights. For example, if there are some network environment upgrades, the personnel in the industry will not change, and the outsourced colleagues will need to re-apply for access rights. In fact, it is different from the level of the company. The authority of the account in hand is also different.
After thinking about it, I am still ready to improve myself.
My journey from functional to automated
I am also a black box, and I wrote test plans, test cases, and manual points for more than two years; until I really hated this mechanical mode.
Until... the company recruited an automation boss, thank you for guessing, I did not learn from this boss, I just saw that this boss seemed to get a very high salary, as a child, I can only, only~
Then envious start~! Wow, let's start writing interface requests in Python^^
Fortunately, the whole process of this company that let me perform manual testing is relatively standardized, the overtime is not too much, and the atmosphere is relatively good, so the Python interface request is written very well!
However, after my boss saw my code, he sighed~, it's okay for the first time.
As a member of black box testing, I have accumulated a series of good process concepts/writing standardized test plans/test cases and reports, etc.
Therefore, in the second year of the black box, I have taken the initiative to refer to the online tutorials, and according to the business assigned to me by the company, I wrote the interface automatically (pure code mode) at my own convenience.
My job search starts with automation
After leaving the company that wrote the python interface request, I started to write my own resume that I wrote automation on my resume.
Of course, as reflected in your resume, you must also ensure that you do have automatic thinking, so I usually study this series of articles online and watch how others operate in practice.
This means that the resume should not be falsified, at least there is a little ink in the stomach.
Fortunately, the next company came to me. The position is indeed automated, but what I do after entering is test development.
[How to say the difference between test development and automation, I think, the scope of automation will be wider than that of test development].
Moreover, this company opened a salary that I didn't expect, and I was really happy to fly.
At the end of the interview, I called back to my mother and said: This company is very big, of course it is great to be able to get in, but I should not be able to get in, I think my interview is not very good.
This company is also very efficient, and informed me that I was hired the next day.
This company has taught me so many things, including of course the wonderful competitive relationship in the workplace.
In this company, I really played with servers, server flashing, group raid, etc., and also automated the interaction between different systems [the company's products are relatively complicated, combining software and hardware].
At the same time, I also participated in the analysis of some competing products/participated in product design, etc., and walked on the road of product thinking, so I always emphasize: testing should not be just testing~
At the same time, there are customers who I hate on-site to implement deployments. In short, I have experienced several different lives.
pressure
After I joined this company, the biggest change was the pressure. In a certain year, my hair grew gray.
I always think about the code during the day at night, how to write it, how to design and adjust the architecture, and then I lose sleep.
This pressure also caused a voice in my heart: Do you want to resign?
Fortunately, I persisted for a few years and learned what I can learn
study
I want to say that if you are in any company, don’t say that you can’t learn anything, but think about it: what can you use from this company to improve yourself.
Enterprises can provide projects, this is true, what can you learn from this project, what kind of ideas can you develop on the premise of this project.
Enterprises can provide servers, can you handle common shell commands on this basis? Commonly used bat commands?
In short, you want to write, and the open web can provide most of the information you want.
However, the so-called mentor, a good mentor is just a guide, everything depends on yourself.
future
A lot of people will ask the prospect question~
The problem of development~
I’m sorry that everyone’s vision is different, do I stick to this path, what will I do in the future, haha I don’t know~~
However, if you implement everything carefully, there will always be no mistakes. Since you have done it, don’t be the last one~
Learning is like sailing against the current, if you don’t advance,
you will retreat. You can’t stop learning at any time, especially in the rapidly developing Internet industry. Of course, learning is necessary, but don’t blindly follow the trend of learning. The higher the salary, the more you need to delve deeper into one or several specific fields. Continuous learning in fields that you are familiar with and have a working background is the key to career development. efficient way.
Of course, the real opportunity to solve the problem still comes from work. Regarding skill improvement, whether it is self-study or participating in a training institution, you need a correct direction to guide you to learn, so that learning will be easier. Take unnecessary detours, so thinking is very important.
My road to automated testing is inseparable from the plan at each stage along the way, because I like planning and summarizing, so my friends and I spent a period of time to organize and write the following "Automated Test Engineer Learning Route", also A lot of [network disk resources] have been sorted out, friends who need it can continue to read. Hope that gives you help and direction...
1. Python programming from entry to proficiency in basic/advanced/object-oriented/automation related...
Advantages of Python in test engineering
Free, open source, easy to learn, powerful library, well integrated with other languages.
It can be said that when you first start doing automated testing, there is no problem at all with Python, and various testing frameworks (unittest (python), pytest (python), JUnit (java), selenium, appium) can handle it.
The knowledge points that need to be mastered are as follows:
2. Practical topic of interface automation test project-Requests/Pytest/Yaml/hot loading...
Interface automation is to maintain and test the functions that we have developed and launched. First, maintain the availability of our existing functions. Second, detect whether the newly developed interfaces have an impact on the original functions after deployment, causing Legacy features are not available.
The knowledge points that need to be mastered are as follows:
Basic interface principles and tools
The next step is the unified encapsulation of interface automation, the knowledge points in it are very detailed
3. Practical topic of WEB automation test project – Selenium/POM/Keyword Driven/Grid...
To put it bluntly, let browser automation replace manual or functional test cases, so what technologies do you need to master?
The knowledge points that need to be mastered are as follows:
Basics - Knowledge
Purchase price - the knowledge points of the third-party library need to be mastered here
4. Practical topic of APP automation testing project – Appium/Uiautomation/Minium...
How to put it, the tools used in the web automated testing of mobile clients and small programs include appium automated testing
The knowledge points that need to be mastered are as follows:
Five, DevOps system topic for test development - Git/Flask/Jenkins/CICD/Docker...
Here is not a brief introduction, you can intuitively look at the knowledge points
The knowledge points that need to be mastered are as follows:
6. Practical topics on commonly used automated testing tools-RF/Postman/Httprunner/microservices...
The knowledge points that need to be mastered are as follows:
Seven, Jmeter performance test project actual combat topic-Jmeter pressure test/database performance/Grafana...
The knowledge points that need to be mastered are as follows:
Summarize
If you are proficient in the above seven topics, you will not go if your basic salary is less than 20k. Of course, the salary here is also in first-tier cities. It also depends on how well your resume is written and your interview performance. The sum of 20k is about the same.
Finally: The complete [Software Testing] video learning tutorial below has been sorted out and uploaded, and friends can get it for free if they need it [Guaranteed 100% free]
Friends who need this document or other software testing learning resources can click the small card below to enter the group for free~