I'm from a black box too.
Now when I go to a company, someone will ask me: Were you a developer before? How did you become so powerful? In the end how to learn it?
I also came from a black box, don’t underestimate the ability of testing, fortunately, I came from a computer major, this foundation has brought me a lot of advantages; in fact, many times, I myself regret it, come out Why didn't I choose to become a research and development at the moment, but chose to test.
In fact, the more you get to the back, the more you will understand that it will be easier if you start with R&D and switch to test development. Why didn't you choose to code in the first place? The same idea: I really didn't like coding when I was in college. I thought it was easy to get started with testing, and there were fewer opportunities to move code; but wow! After work, in order to increase my salary, I forced myself to learn coding~Khan
At the same time, I also prepared a software testing video tutorial, which is placed at the end of the article. If you need it, you can watch it directly, or directly click on the small card at the end of the article to get the information document for free
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 seems to have a very high salary, and I can only, I can only~ So, I started to write in Python interface request ^^
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 writing my own experience writing 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 belly.
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 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 have always emphasized: 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 rowing upstream
Never stop learning, 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.
the right way to study
Finally, I will share the [Preparation Resource Library] that I have compiled , which basically covers all the core technical points of software testing: testing theory, Linux basics, MySQL basics, Web testing, interface testing, App testing, management tools, Selenium related, performance testing, computer Network, principles of composition, data structures and algorithms, logic problems, human resources, technical brain maps, etc ... the quality is very high! ! ! More than enough for technical interviews! [Click on the small card at the end of the article to get it for free]
1. Fundamentals of software testing
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 capabilities.
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 automation test Java&Python
Understand the purpose of automation, master TestNG&unittest automation framework, and 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!
Reasonably use every minute and every second of time to learn to improve yourself, and don't use the reason of "no time" to cover up your ideological laziness! While you are young, work hard and give an explanation to your future self!
Where to watch the video tutorial:
Big Byte teaches you to quickly master automated testing in one month, and there is no nonsense in the whole process! Securely get a high-paying offer after finishing your studies, and go whoring forever! _哔哩哔哩_bilibili [Software Testing 1000 Episodes] Big Byte teaches you to quickly master automated testing in one month, and there is no nonsense in the whole process! Securely get a high-paying offer after finishing your studies, and go whoring forever! A total of 93 videos, including: [2023 Study Plan] Find your salary and position, [2023 Study Plan] Interview-oriented learning, [2023 Study Plan] work-oriented study, etc. For more exciting videos, please follow the UP account . 
https://www.bilibili.com/video/BV1ZF411d7fX/?spm_id_from=333.999.0.0&vd_source=74d0257ec7066cc4f9013524f0bb7013 I also prepared a copy of "Software Testing Interview Collection" for friends who are going to interview, hoping to help you!
The entire document has more than 200 pages in total, and it is definitely unrealistic to show you all. In order not to affect your reading experience, only part of the content is shown. I hope you will bear with me. I hope it can help you review before the interview and Find a good job, and save everyone's time searching for information on the Internet to learn! I hope everyone can gain something!
