foreword
When I usually communicate with my colleagues, someone raised such a question: When can the test be done? This question is also asked by many testers and wants to know the exact answer.
I asked some friends who have just entered the testing industry. Some said that if the code is good, they can be transferred to development. Some said that the development is the same and they will be eliminated. However, it is easy to transfer from development to testing.
I have asked many friends, and most of the feedback given to me is that the status of testing is far inferior to that of development, and the right to speak is completely different, and anyone may be eliminated at the end. As far as we are concerned, the way we think about problems cannot be generalized in such a big way. If you want to change, you must start from the subtleties.
I've had some successful ones and some failed ones.
Successful ones often have a lot of foreshadowing before switching, such as studying prd and product logic when testing requirements, and then switching to BA. For example, some wrote a lot of engineering code during the test process, and later transferred to development or test development. Those who failed to transfer, I won’t say much, there are too many, basically they didn’t make a name for themselves, and their minds changed industries. [I have prepared software testing materials for you at the end of the article]
What should I do in the early stages of my career?
In the first 3 to 5 years of my career, I personally feel that I should do more and exercise more. Accumulate your own abilities first, reflect your value, and then talk about salary (you still have to eat). When I first entered the workplace, I constantly improved myself by doing things, and reflected my own value by solving problems. Doing things is a kind of resource in itself.
When I first started, I grew up in continuous learning and problem solving. I learned performance testing first, and then tried it in a group. Later, when the company needed it, I formed a small performance testing team to solve performance problems. In order to improve my coding ability, I threw myself into the development team, started from the bottom, and coded for more than a year, laying a solid foundation for subsequent testing and development. Once you get in touch with DevOps-related knowledge, you will learn to get a certificate, and then you will have the opportunity to be a platform and do performance. I have spent all this time dealing with things. In many cases, the salary and ability do not match, and others do not know how capable you are, so you need to test your level by doing things.
" Someone pays you to improve yourself, why not do more?" In addition to doing your job well, you can actually do more things and accumulate more experience. If you don't do well, there is a high probability that you won't need to pay directly. Isn't that good?
Always pay attention to the development of the industry and maximize your strengths
After the accumulation in the early stage, you have a certain understanding of your own ability, combined with the development trend of the industry (you must pay more attention to the industry dynamics, with the help of the development of the industry) , at this time, in addition to doing things, you have to stop and think about which direction you should go for directional accumulation. Don't make up for your own shortcomings, but give full play to your strengths, and then use this strength to the extreme. Now that the division of labor is becoming more and more detailed, personal shortcomings can be made up by the team, but your strengths must be irreplaceable in the overall team, so that there will be better room for development.
I think this stage is actually the most difficult, because there is no clear goal, and the decision may be wrong. At this time, you can listen to the opinions of your seniors. If conditions permit, you must find the best people in the industry to give you advice. Their structure and vision largely determine your upper limit.
By the way, pay attention to accumulating transferable capabilities. For example, in the process of learning performance testing, you may pay attention to the use of various tools and commands in the early stage, including tuning routines. This is very important, but not the most important, because this kind of ability is not transferable. If you change tools, you have to learn. Similarly, these tools are limited for you to solve other problems.
However, the ability to analyze performance problems, the ability to coordinate the performance testing process, and the ability to communicate with others to solve problems, etc., are all transferable. Analysis of performance problems can improve your logical ability, because performance problems involve too many aspects and require you to do more coordination and communication. These abilities need to be exercised and cultivated more deliberately to lay a more solid foundation for your future development. When you get older, it's these soft skills that you work more on.
Early accumulation is the premise of your later negotiation
In fact, in essence, the previous accumulation is for you to have more choices in the middle and late stages of your career. We should not only consider problems in the workplace, but also family, parents, social environment and other issues. We have to keep doing multiple-choice questions (except for mines at home). At this time, whether we have the ability and power to choose becomes particularly important. Having no choice is the scariest and saddest thing.
With the previous accumulation, you will have the premise to bargain in the workplace. Although you will pay a certain price, it will not deform your choice (for a salary, you will be PUA, but you can’t give up the stall, and then make compromises, but also feel unwilling, infinitely entangled, and fall into an endless loop)
Why are you worthless? How to break out of the predicament?
Recently, due to environmental problems, many people are unemployed at home. When looking for a new job, the salary is not ideal. Many people wonder why they are suddenly "worthless". In fact, it is not your value that determines your price, but the relationship between supply and demand. When the industry was just developing, you could get a good salary without much ability. Now the industry has transitioned to a stable period, and there are no too high bonuses. The supply exceeds demand, and no matter how good your ability is, you may not be able to get a satisfactory salary. The industry is developing, and everyone rolls together.
To maintain the ability of continuous learning, always pay attention to the development of the industry, if possible, try to develop your own second career curve. Keep an open mind, constantly accept new things and new ideas, be curious about all new things, and be able to actively solve problems, see things beyond your own vision, keep updating your thinking structure, and get out of your comfort zone.
What should I learn to continue studying?
Many people don’t know how to learn and what route to follow, so I collected and sorted out some software testing resources [click the small card at the end of the article to get it for free], which basically covers all the core technical points of software testing: testing theory, Linux foundation, MySQL foundation, Web testing, interface testing, App testing, management tools, Selenium related, performance testing, computer networks, composition principles, data structures and algorithms, etc. I hope to record what I have learned and the technologies and learning methods used in actual work . I also hope that through my sharing, you can avoid some detours, form a set of your own methods, and apply them in practice.
Software Testing Learning Route
1. Pre-basic knowledge
Computer Basics
test theory
HTML basics
CSS basics
JavaScript basics
Two, linux and database
linux
Database introduction
SQL language (emphasis)
Advanced Database Features
3. Programming language
Python basics
object oriented
exception handling
Modules and Packages
4. Interface test
Interface Basics
Postman implements interface testing
database operation
Code implementation interface testing
continuous integration
Interface Test Extension
Five, WEB automation
Getting Started with WEB Automation
Basics of WEB Automation
WEB Automation Intermediate
WEB Automation Advanced
Project combat
6. Mobile automation
Basics of Mobile Automation
Mobile Automation Intermediate
Mobile Automation Advanced
Seven, continuous integration
Jenkins Continuous Integration
DevOps-CI/CD automated testing pipeline
8. Performance test
Basics of performance testing
performance testing tools
APP performance test
Performance Test Tuning
Nine, ten actual combat projects
Reading house novels, wealth management and financial platforms, B2C online shopping malls, security testing actual shooting ranges, automated testing platforms...
I help you technically
I have compiled a set of software testing interview documents and a set of software testing resources for you , with a total of 608G . It should be of great help to friends who want to change jobs for interviews, get promoted and raise salaries, get rid of career difficulties, and improve their skills. I hope that everyone can have a bright future. [Click on the small card at the end of the article to get a full set of software testing materials for free]
