Let me talk about my past. I have been engaged in Oracle development for more than two months since graduation and then transformed into software testing. It has been nearly 8 years since I grew up as a test development engineer. A little reference for students before development and testing.
1. Foreshadowing of the road to testing
I was lazy in school and left a habit of reading other people's code. Many times I feel that other people's writing is much better than myself. A simple piece of code written by others is exquisite, while my own is ugly and long. Look at the code with a critical eye.
The logical thinking ability is relatively OK, especially the divergent thinking. Almost all the written test questions in the job interview are logic questions. I completed them all correctly at a very fast speed. Compare concealment and concentration, conduct different tests from different directions, find problems and bring out series problems
(I once tested a functional module that had a problem and submitted some problems. At that time, the pressure of the project made the test and development a little atmosphere. I was called by the supervisor to criticize. I wrote too much, and the development felt that the things mentioned in it were correct. Yes, it has been verified that some of the problems are hidden problems, and it is not easy for the supervisor to praise after criticism, but it was very good to tease me in those two weeks).
I have perfectionist tendencies (bad habits in life), striving for perfection, and this has caused me some minor problems. If there are some small problems in the things I write, I will be very discouraged. Testing to find out the mistakes of others will give me a sense of accomplishment. I also know that being able to tolerate imperfection is perfection, and the goal of hard work.
I'm not as passionate about development as I am about testing.
My development ability is average, not outstanding. Software testing is complex. Breadth and width are required, followed by depth. Although I took the initiative to help the development to handle the exceptions in the database during the test, when I first proposed a solution, the development did not agree with a test plan, but later adopted it. The developer no longer underestimated me.
2. Summary of the road to testing
Software development is constructive, but software testing is destructive on the one hand. Development focuses on design, so that the program does what it should do and does not do what it should not do. Generally speaking, after the development and writing of the program, it will Verify whether the program does what it should do. Software testing not only verifies whether the program does what it should do, but also pays more attention to whether the software does what it should not do. So testing is more concerned with whether the software does something it shouldn't do.
Verify that the implemented functions are correct, and verify that the functions are implemented correctly.
Negating themselves again, the low efficiency of developing and testing their own code is because deep down they are unwilling to deny themselves and feel that they have problems. Testers should learn to deny themselves, so that in the process of regression testing from one version to another Make sure your tests are spot on.
Never think that software quality is the task of software testing, and don’t take the blame easily. Software quality is determined by the system architecture of development from the very beginning. Software testing is just to optimize and improve the quality of software, but there may still be fatal bugs. So do a good job of your own management and evidence, so as not to let yourself be easily blamed. Of course, in his position, to find his job, the test must be full of strong sense of responsibility. Be careful with your work.
To learn more, you must affirm your ability in the test. Maybe my ability is not developed in the eyes of others, and it is very dazzling in a certain aspect. I have always been full of confidence in myself. The test requires my own breadth and mentality. Practice is more needed. Like an iceberg, huge business knowledge, testing framework, and multi-dimensional thinking habits seem to be point by point. When you connect these points, you will see a vast ocean. Therefore, you must Learn, learn more.
Communication is very important, a lot of communication, and the art of communication is even more important. Getting along with development can bring a lot of fun to work. In many cases, the developers you communicate with during your day are basically developers. Learn to be tolerant and understanding.
At present, I am only in the black box stage, and I also want to learn more and more testing tools and scripting languages, but I can't underestimate myself. Whether it is automated testing or manual testing, it is essentially a testing method, and testing tools are just carriers. Second-rate. If the level is not enough, you may not be able to use and know how to use even the most powerful testing tools, but you must learn more about it.
Three, 8 years of transformation, now it is almost test development, with an annual salary of 30W+
After 8 years of transformation, I have grown from a junior test engineer to a test development engineer
Daily work content:
Write automated test scripts: Test development engineers need to use programming languages (such as Java, Python, etc.) to write automated test scripts to perform multiple test stages such as system function tests, performance tests, and interface tests.
Build an automated test framework: Test development engineers can use open source test frameworks or build test frameworks by themselves to improve test efficiency and maintainability. Some commonly used testing frameworks include Selenium, Appium, JMeter, Robot Framework, etc.
Analyzing test results and problems: Test development engineers need to analyze the results and logs of automated test scripts to find out where the problems lie and give timely feedback to relevant developers or testing teams.
Collaborate with the development team for integration testing: Test development engineers need to work closely with developers to conduct integration testing to ensure the coordinated operation of various components of the system.
Participate in continuous integration and continuous delivery: Test development engineers need to participate in continuous integration and continuous delivery processes to ensure software quality and stability. This includes building a test environment, formulating a test strategy, and continuously monitoring and optimizing the test process.
In short, the daily work of test development engineers is mainly automated testing, and they also need to have skills in software development and test management.
END meager strength
Finally, I would like to thank everyone who has read my article carefully. Seeing the fans’ growth and attention all the way, there is always a need for reciprocity. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for friends who want to advance [automated testing]. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you too!
