This decision has been on my mind for a long time. It wasn’t until some time ago that Byte was trending and I resigned... I
still mustered up the courage to write this article. It can be regarded as finding a new goal and having the courage to start again.
After graduating in 2017, I joined Didi, and then switched to Byte, where I have been engaged in software testing. No previous internship experience
I graduated more than 4 years ago and am working in a testing position. I have worked in many small and medium-sized companies before. In fact, I had a relatively good understanding of Byte’s values and atmosphere before joining...
The reasons for choosing to remove bytes are as follows:
Judging from the job position, Byte is considered a first-tier manufacturer. Go in and experience learning, and get gold-plated by the way.
My inner recognition of myself is that if I can pass Byte's technical aspects, I can't say that I am very good, but at least I am not a parallel importer.
My parents hope I work in a "respectable" place... Bye is quite respectable in their circle, and it seems that their children are very hard-working.
In short, for all the above reasons, I prepared carefully... and finally passed the interview with Byte. I was still very happy at the time and I was very satisfied with the salary.
I completed a promotion and changed companies. There were times when I was happy and contented, and there were also days when I was confused and struggling. However, I managed to transform from a newbie in the workplace to a senior paddler fairly smoothly.
1. From thinking it was God’s favor to not adapting
In the first few days when I joined the company, I was very excited. I got familiar with the company environment with my colleagues who joined the company, and helped him solve some technical problems... However, in the next two months, although I was mentally prepared, I was still very Not used to it.
I still feel very uncomfortable with the entire culture and everyone's behavior.
First of all, there are many meetings. A meeting often lasts for 2 hours, and everyone likes to interrupt and slow down the progress of the meeting. Small questions that can be counted clearly in three sentences are stuffed into various high-level word combinations and reorganized into articles. It’s a big composition. After a few meetings, I felt like I was stupid. It was a feeling of complete confusion!
At the same time, I was assigned several pieces of business shortly after joining the company. After that, people related to these businesses all came to you when they had problems. It was common for two-digit people to come to you every day to solve problems... And I was also a newcomer, so I didn’t understand many things. My senior brother who had just joined the job was assigned to another job. I feel quite isolated and helpless. When I ask questions for help from the group, I often get the reply "If you don't understand this business, go and learn about it as soon as possible"...
I have no choice but to bite the bullet, because Byte uses many self-built tool libraries and frameworks internally, and many tool documents are indeed not very good. Many times, you have to ask the maintainer directly. Then when you ask, the other person will see you as a new person and will most likely have read it for several hours without replying... In short, it is very difficult and inefficient to solve the problem, and you often get criticized directly.
2. Resign decisively
During this period, I also took another test. The test was originally a small thing, but as I continued to test it, I found that it was different from what was promised. Many things that should have been tested were not done. So I raised this question to other team members, and the reply was, "Test it, and retest a certain piece of xxx by the way." As a result, what was originally a small problem turned into a slightly disgusting bomb, and in the end it was not easy. It's done. Looking at the colleagues who joined me together, I felt that the work they were responsible for was much easier to deal with than mine, which also made my originally unstable mentality even more explosive.
This situation lasted for a month. One night, I asked an acquaintance about the situation. As soon as he heard about the business I was responsible for, he immediately reflexively said, "This is a shit basin." I was shocked when I discovered that several of the businesses I was responsible for were recognized pitfalls. They were filled with trivial needs and deep pits, and it was difficult to measure any results.
After learning the news, I wandered around downstairs for a while after dinner, hoping to calm down, but the more I thought about it, the more headache I got. So I went upstairs again, turned on the computer, and found a lot of unread messages on Feishu. After a quick glance, the screen was full of:
"Help and take a look", "We have a problem with xxx, please help solve it quickly", "Test xxx", "There is a problem with your xxx, please help and take a look", and several groups filled the screen Positive thumbs up…
At that time, I felt like I took a breath of cold air and was in a trance. In fact, a few days ago, I felt like going to work was like going to a grave. I felt like there was a ghost following me every day, and my brain was always in a high-pressure and tense state. Although I should be able to continue to resist these things for a while, I really don't like this style of doing things. I feel that if something goes wrong, everyone is trying to find a way to blame it and find the person responsible. I didn’t think I could transform into a person who could fit in with this kind of atmosphere, so I thought about it and decided to leave my job after I went back that night!
In this process, I summed up some practical paddling experiences. Some of them were learned by myself, and some were learned from communicating with others. I would like to share them with you here.
The advice I give is similar. If you are currently in an outsourcing company, study more and strive to improve your skills. You must also clarify your career plan so that you have the capital to change jobs and have the opportunity to compete with others.
Here I share with you a complete set of test materials. This note has been of great help to me in my study. If necessary, click on the link below to join the group to receive the information package. They are all shared for free!
1. Learn to think deeply and summarize
The first thing I want to say is to learn to think deeply and summarize. This is the most important and meaningful thing in my opinion.
First let’s think deeply. In the circle of programmers, you can often hear some comments: My job has no technical content at all. I just do a little bit every day. What can I learn from this? Put aside some ridicule and joking arguments, this Maybe it is indeed the true thoughts of some classmates, at least I used to think so. Later, with the accumulation of work experience and discussions with some high-level classmates, I found that this idea was actually very wrong.
The idea that there is nothing to learn is basically the result of lazy thinking. Any seemingly inconspicuous little thing, as long as you think deeply and dig a little deeper vertically or broaden horizontally, it is an ocean of knowledge that is enough for people to indulge in.
Let’s talk about the summary . I think this is where most programmers are lacking. They can do one thing very well just by immersing themselves in work. But I almost never make abstract summaries, so that after working for several years, the knowledge I have mastered is still sporadic and unsystematic. Not only is it easy to forget, but it also causes my vision to be narrow and my view of problems to be limited.
It is very important to make some summaries and reflections in a timely manner. This is a process from technique to Tao, which will allow you to see the problem from a wider perspective and at a higher level. When encountering the same type of problems, you can follow the summarized methodology to advance and solve it systematically and hierarchically.
As an example. For background services, 1G of memory was optimized today and 50% of the reading and writing time will be optimized tomorrow. Can you summarize the performance optimization?
For example, at the application layer, you can manage the applications connected to the service and sort out the rationality of their access; at the architecture layer, you can do caching, preprocessing, read-write separation, asynchronous, parallel, etc.; at the code layer, you can do things There is more, resource pooling, object reuse, lock-free design, large key splitting, delayed processing, encoding compression, gc tuning and various language-related high-performance practices... I will meet you next time For scenarios that require performance optimization, a whole set of ideas can be applied immediately, and the rest is a matter of tools and practical operations.
Some students said that I would argue with the PM every day to work on the requirements and not do any performance optimization. Let’s not discuss whether performance optimization can be done. In terms of business needs alone, there are also things that can be summarized. For example, how to build a system? Have you thought about the core capabilities of the system, system boundaries, system bottlenecks, service layering and splitting, and service governance? You discuss the requirements with the PM every day. How should you, as a technical student, cultivate product thinking and guide you? Product trends, how to make architecture precede business, these issues can also be thought about and summarized, right?
Therefore, learning and growth are a self-driven process. If you feel that there is nothing to learn, it is most likely not because there is really nothing to learn, but because you are too lazy, not only too lazy in action, but also too lazy in thinking. Too lazy.
You can write more technical articles, share more, and force yourself to think and summarize. After all, if the article is not deep enough, everyone will be embarrassed to share it publicly.
2. Actively learn and maintain enthusiasm for technology
An anxiety theory that has been widely circulated in the Internet circle in the past two years is called the 35-year-old programmer phenomenon. The general idea is that programmers who work in this industry until they are 35 years old are basically waiting to be laid off. It is undeniable that the Internet industry is indeed inferior to civil servants and other institutional professions in this regard. But the 35-year-old programmer in this question is not 35 in the absolute physiological sense. It should refer to those programmers who have worked for more than ten years and who have worked for two or three years. There is not much difference. The following jobs are basically resting on one's laurels without taking the initiative to learn and recharge. 35 years old is almost the same as 25 years old, and there is no desire for learning and growth at 25 years old. Instead, many trivial matters in family life are added, and salary requirements are often higher. It seems to the enterprise that this is indeed not very competitive.
And if we actively learn and keep our technical capabilities and knowledge reserves proportional to our working years, how can we have any anxiety when we are 35 years old? I think major companies should be rushing to get such experts, right? But learning is a matter of , is actually an anti-human process, which requires us to force ourselves to jump out of our comfort zone, take the initiative to learn, and maintain technical enthusiasm. There is a saying in Didi that goes something like this: Take the initiative to step out of your comfort zone and feel struggle and pressure. It is often the darkness before dawn, and that is when you grow the fastest. On the contrary, if you feel that you are living a comfortable life every day and that your work is just messing around with your hours, then you may be boiling a frog in warm water.
During the period after graduation, you often have more free time, which is a good time to work hard to learn technology. Use this period of time to lay a solid foundation, develop good study habits, and maintain a positive learning attitude, which should benefit you throughout your life. As for how to study efficiently, there are many experts writing such posts on the Internet. After arriving at the company, you can also find many such sharings on the intranet, so I won’t go into more details.
3. Take the initiative and communicate feedback in a timely manner
The first two are from a personal perspective. I hope everyone can improve their personal capabilities and maintain core competitiveness. But from a company's perspective, when recruiting employees, the most important thing is for them to create business value and contribute to the company. Serve.
Although there is generally a certain training system for school admissions, in fact the company does not have the obligation to help us grow. When it comes to being able to accomplish things and create value for the company, I think the two most important words are taking the initiative, taking the initiative to take on tasks, proactively communicating, proactively promoting project progress, proactively coordinating resources, proactively giving upward feedback, and proactively creating impact. Power and so on.
When I first joined the company, I basically did my job well according to the tasks assigned by the leader, and then did my own thing. I almost never took the initiative to communicate with others or actively think of ideas that could help the development of the project. I thought that it was enough to complete my job with quality and quantity, but later I found that this was actually not enough. This was only the most basic requirement.
Some students' approach is that the leader only needs to synchronize what direction they want to take recently, and the leader basically does not need to worry about the following series of things. I am a leader like this classmate, and I also like it. A word you often hear after joining a company is owner awareness, which probably means this.
Another very important point in this process is timely upward communication and feedback. If the project is not progressing smoothly, if you encounter any problems, synchronize with the leader in time. If you are not sure about the technical solution, you can discuss it with the leader. If you cannot coordinate some resources, you can ask the leader for help. Don't have too many scruples, thinking that these will be too troublesome. Leaders actually do what they do. This matter.
If the project is progressing smoothly and there is really no need for the leader to intervene, then it is also necessary to provide timely feedback on the progress of the project and the benefits achieved. If you have any ideas, you should also discuss them. Ask the leader for his suggestions on the current progress and what other areas there are. Needs improvement to eliminate information errors. Doing these things, on the one hand, makes reasonable use of the various resources of the leader, and on the other hand, it also allows the leader to understand his workload and control the overall project. After all, the leader also has leaders, and they also need to report.
Maybe it’s the upward management that everyone dislikes. It’s a bit offensive. I actually don’t do this well either. But the most basic point is, don’t accept a task and work sullenly or even isolate yourself from the world. You haven’t synchronized with the leader for a month, thinking about holding back a big move or something, that’s basically cool.
You must take the initiative. You can start by forcing yourself to speak in various public places. If you have questions or ideas, you can do so one-on-one.
4. A set of good materials to systematically improve learning
Finally, you need a set of good information for system improvement to improve your comprehensive technical capabilities!
As a tester, I would like to share some of my summary and summary of technology over the years, as well as my notes on the skills that need to be mastered as an advanced automated tester. I hope it can help those who are interested in this road of technology. Friends who go all the way to the end!
1. Testing Basics
Understand the basic skills of testing, master the use of mainstream defect management tools, and be proficient in the operation and maintenance of the test environment
| Programmer Uncle Lei | Test basics |
|---|---|
| Test plan/test case | Black box use case design equivalence class/boundary value/scenario analysis/decision table/cause and effect diagram analysis/error inference |
| defect | Defect life cycle/defect classification/defect management tool ZenTao/Jira |
| database | Mysql/environment setup/add, delete, modify/query/associated query/stored procedure |
| Linux | System setup/basic instructions/log analysis/environment setup |
2. Necessary knowledge of Linux.
As the most popular software environment system, Linux must be mastered. Current recruitment requirements require Linux capabilities.
| Programmer Uncle Lei | Linux essential knowledge |
|---|---|
| Linux system introduction and preparation | As the most popular software environment system nowadays, you must know how to learn Linux. You will start with the introduction of the CenterOS version system, installation, directory structure and other basic contents, and also prepare for the subsequent self-built test environment. |
| Linux remote tool Xshell | Detailed introduction on how to get started using Linux and perform regular remote management and file transfer operations, including the tools Xshell and Xftp |
| Linux file attributes and management | Linux files, basic directory attributes, file operations, file management, directory operations, directory management. Avoid self-destructive operations and how to prevent accidental operations |
| Linux user and group management | How to add, delete, modify users and groups in Linux, and grant corresponding permissions, so that you no longer get stuck due to permission issues |
| Linux file editor | The use of Linux file editor vi, command mode, input mode, operation examples, shortcut keys, pipe commands, usage experience. How to edit in a system without graphics? |
| Linux common system settings | Network settings, environment variables, disk management, time settings, system resources, firewall, everything is available, don't worry about being clueless. |
| Linux installation software | Linux installation commands, and how to install through installation files downloaded from the network such as tar, gz, etc., such as MySQL database installation. |
| Linux Docker container | Explanation of Docker container technology, image management, warehouse, container creation, startup, operation, image packaging, and catching up with popular industry technologies |
3. Shell Script
Master Shell Script: including Shell basics and applications, Shell logic control, and Shell logic functions
| Programmer Uncle Lei | Shell |
|---|---|
| Linux Shell Basics and Applications | Introduction to shell script programming, environment types, variables, parameters, operators, use of arrays, close contact with scripts |
| Linux Shell logic control | Shell logic application, test command, process control, data input and output, script logic is no longer monotonous, and you can play tricks |
| Linux Shell functions | How to write shell script functions, call files to each other, and apply scripts in practice. What can you do if you know how to develop, test, and operate? |
| Windows Script Batch | Enough playing with Linux, let’s take a look at the usage of regular Windows commands, how to write batch scripts, and practical applications. Linux is not everywhere. Windows scripts are also one of the commonly used scripts. When you see this, you may use Windows. |
4. Internet Program Principles
The only way to automate: basic knowledge of front-end development and essential knowledge of Internet networks 4. Internet Program Principles
| Programmer Uncle Lei | Internet program principles |
|---|---|
| Web front-end development basics | Learn basic content of HTML and CSS. Why were test courses developed? Sorry, if not, automation may not be welcome. Many automated testing problems arise from the development foundation. |
| Web front-end development script | JavaScript is the most mainstream script learning. Similarly, this will also be involved in automated testing. In fact, dynamic scripts are often used in some tools, and they are also JavaScript languages. |
| Developer debugging tools for testing applications | Although the browser's F12 is named a developer tool, testing actually plays a key role in both functional testing and automated testing. Such as parsing HTML, locating elements, debugging scripts, monitoring network packet capture, etc. |
| Internet program network architecture | Understand the birth of Internet programs in detail through network architecture, logical details, how Internet communication principles transfer data to other computers, and what is the relationship between TCP, UCP, HTTP, and other protocols. |
| HTTP protocol data structure analysis | Completely analyze the HTTP protocol data structure, including Request and Response data formats, the definition and usage of Header, what each status represents, and how to identify errors. Analyze the position of parameters in the protocol, rest structure, various common body data forms, parsing methods, and causes of common data parsing errors. |
| Cookie and Session mechanism | Interpret what Cookie is, what relationship it has with Session, how to test Cookie and Session, and what you need to pay attention to |
5. MySQL database
software testing engineers must have MySQL database knowledge, not just the basic "add, delete, modify and check".
| Programmer Uncle Lei | MySQL database |
|---|---|
| MySQL database testing application | MySQL environment construction, basic use of client Navicat and data operations, learning and consolidating basic SQL syntax, adding, deleting, modifying, and checking are indispensable, and mastering the usage of various conditions |
| MySQL advanced query | Query upgrade, master multi-table query, subquery, query grouping, use of statistical functions, and study and analyze classic interview questions |
| MySQL custom function | Since there are built-in functions, there is certainly no shortage of places for custom functions, which are often used. Just like any development language, they are inseparable from the definition and use of functions. |
| MySQL stored procedure SP | How to define the stored procedure that is essential for the database, usually also called SP? How to test? How to use it more safely, test what else can be done with stored procedures, and more content that is convenient for testing |
| MySQL things and programming | Database transaction use cases, the principle and use of indexes, the application of database SQL programming in testing, and how to use it to quickly and accurately generate a large amount of specified test data |
6. Packet capture tools
Fiddler, Wireshark, Sniffer, Tcpdump and various packet capture tools are suitable for various projects. There is always one that suits you.
| Programmer Uncle Lei | Packet capture tool |
|---|---|
| Principles and methods of packet capture | Only by understanding the principle of packet capture can we truly use a suitable tool and choose the appropriate direction and method, otherwise it will be in vain. |
| Packet capture tool selection | Classification and functions of packet capture tools, which tool is suitable for what kind of project, and how to identify the advantages of the tool |
| Fiddler basic functions | As a professional HTTP system packet capture tool, this article introduces its principle in detail, how to filter data, how to search for the desired data, and how to capture packets in various environments such as web, non-web, mobile phone, HTTPS protocol, etc. |
| Fiddler advanced features | Learn to use it for interface testing, power outage, scripting, etc. to modify and replace data, simulate data for interface Mock testing, and create your own defined menu functions. |
| Wireshark | It is not so much a packet capture, but an analysis tool after packet capture. Under each system, other packet capture tools integrated with the system are used to capture, organize and display data. It has powerful filtering and analysis functions. |
| Sniffer | Black technology packet capture tool, there are many versions, very professional packet capture tool |
| Tcpdump | Packet capture plug-in artifact in Linux and Android series systems |
7. Interface testing tool
Interface testing artifact, a powerful tool that you can’t avoid: Jmeter. Small and flexible: Postman
| Programmer Uncle Lei | Interface testing tools |
|---|---|
| Getting Started with Jmeter Interface Testing | Jmeter简介，环境准备，目录结构介绍 ，如何录制脚本，以及基础组件的使用，线程、作用域、HTTP请求、定时器、断言等等 |
| Jmeter接口测试进阶使用 | Jmeter逻辑控制、前置处理器、后置处理器、监视器、结果树，如何参数化、正则表达式关联、事务、检查点等等。并带领大家对带有token等动态数据的项目进行实战演练 |
| Jmeter接口测试高级功能 | Jmeter脚本思考时间、随机时间、线程启动间隔、并发集合点、联机远程调用，webservice、websocket、jdbc、命令调用等等 |
| Postman接口测试工具使用 | 行业标准HTTP、rest接口测试神器，基本请求、分组保存、动态变量、脚本、数据关联、参数化、自动断言、批量运行、持续集成。思路类似其他接口工具，避免泛滥学习 |
八、Web自动化测试Java&Python
了解自动化的目的，熟练掌握TestNG&unittest自动化框架，以及断言与日志处理
| 程序员雷叔 | Web自动化测试Java&Python |
|---|---|
| 自动化框架思路引导 | 我们做自动化到底为了什么？节省人力、加快速度、还是让机器代替手动、还是提升自我。应该如何建立思路，而非无脑进坑任机器摆布 |
| Java&Python3开发环境及基本语法 | Java&Python开发环境搭建，基础语法入门，让不会代码的以最快速度入门，方便适应后续自动化测试开发内容学习，代码够用即可，并不是学得越多越好 |
| Java&Python3集合类型与面向对象开发 | Java&Python各种基本类型、集合数据类型的理解与操作，循环语句、判断语句，面向对象的开发，函数的使用，类的使用 |
| Selenium3环境与浏览器驱动配置 | 基于selenium3的web自动化环境搭建，正确的浏览器配置，不再为起不了浏览器而烦恼。支持IE、Firefox、Chrome等等 |
| Selenium3多种定位及动态操作 | selenium3常见定位方法，属性和值的获取，如何动态判断不一定存在的元素，复杂的网页结构，需要多步骤操作的元素等等 |
| 特殊情况处理（js、特殊控件等） | selenium3自动化测试中，常见的特殊情况处理，如日期、控件、智能等待、文件上传下载、网页嵌套结构，各种弹窗的处理方式，cookie处理，JavaScript脚本调用等 |
| TestNG&unittest自动化框架使用 | Python unittest、Java TestNG自动化框架的使用，环境处理、基本使用逻辑，数据驱动模型，数据库数据载入等 |
| 自动化框架断言与日志处理 | 自动化中最重要的是什么？作为测试当然是断言，没有断言的自动化毫无用处，如何展示日志与结果是自动化测试的根本 |
| PageObject框架设计模式 | PageObject框架设计模式，到底是做什么的？如何更好的快速管理控件，从此做起 |
九、接口与移动端自动化
专业接口调用、测试解决方案。组建完整的web和接口自动化框架，Appium整体使用
| 程序员雷叔 | 接口与移动端自动化 |
|---|---|
| 接口自动化方案Requests | Python Requests、Java HTTPclient接口框架，都是专业的接口调用、测试的解决方案，使用简单快速，结合工具的使用方式和功能，快速上手并对其操作，解决其中的疑难杂症 |
| web+自动化框架整合 | 自动化测试是相通的，如何将web与接口、甚至更多的测试类型和方向结合起来，组成完整的自动化框架 |
| Appium环境搭建 | Appium环境相对复杂，针对Android系统进行完整的环境搭建演练，解决环境上的问题，并进行基本的自动化操作 |
| Appium自动化实战与框架结合 | Appium整体使用与web自动化类似，引导使用典型功能，并针对一款APP进行实战操作 |
十、敏捷测试&TestOps构建
揭开TestOps的神秘面纱，持续集成Jenkins框架烂熟于心
| 程序员雷叔 | 敏捷测试&TestOps构建 |
|---|---|
| 构建敏捷测试运维架构体系 | 敏捷测试是什么？为什么需要敏捷，行业都提到的devops又是什么？TestOps能做什么 |
| 持续集成Jenkins框架实战 | 持续集成最常见的一套框架，介绍Jenkins操作、权限、系统管理等，常用构建与运行实例讲解 |
| 静态扫描测试Sonar | 一款自动化的代码扫描工具，便捷式快速扫描代码中的问题，做到提前发现，统一规范，自动化中的代码测试神器 |
十一、性能测试&安全测试
软件测试的彼岸：性能测试和安全测试，选个方向努力爬坑吧！
| 程序员雷叔 | 性能测试&安全测试 |
|---|---|
| 性能测试学习路线 | 如何学习性能测试，性能测试到底该怎么学习，使用什么工具？工具并不代表性能，接口的基础对性能测试非常重要，而工具只是辅助，更多的是思路和策略。你不会并不是分析而是准备阶段 |
| loadrunner脱离浏览器录制专题 | IE无法启动被测网站？打不开浏览器？程序无法在浏览器中被打开？这些都没关系，还是一样能录制，但录制是偷懒专用的，对于学习有一定的辅助作用，也会带入无法脱离的坑 |
| 性能测试工具操作实践 | loadrunner、jmeter，有了前面的基础使用，看懂脚本不是问题，带上关键的参数化、动态数据关联、事物、日志，大部分的脚本都可以搞定进行实践 |
| 系统监控方案实施 | 工具自带监控？系统监控？JVM内部监控？数据库监控？各种监控的意义何在，如何在各种情况下精准监控数据 |
| 安全测试起源与工具介绍 | 应该如何进行安全测试，安全测试都有哪些分类？都会用到什么样的工具，各自的作用又是什么，如web漏洞扫描，端口扫描，系统扫描等 |
| web安全测试手工实战 | 接口测试在安全中的作用，不会手动的安全测试，那就永远无法理解自动化以后产出的结果 |
| 安全扫描工具测试实践 | 实际介绍以及使用APPscan、awvs等专业安全扫描工具 |
| 企业安全建设（SDLC） | 企业应该如何进行安全建设，制定更安全的软件生命周期。从哪些方面进行着手 |
上面就是我为大家整理出来的一份软件测试工程师发展方向知识架构体系图。希望大家能照着这个体系在3-4个月完成这样一个体系的构建。可以说，这个过程会让你痛不欲生，但只要你熬过去了。以后的生活就轻松很多。正所谓万事开头难，只要迈出了第一步，你就已经成功了一半，等到完成之后再回顾这一段路程的时候，你肯定会感慨良多下面分享我整理的这份2023年可能是最全的软件测试工程师发展方向知识架构体系图
感谢每一个认真阅读我文章的人，礼尚往来总是要有的，虽然不是什么很值钱的东西，如果你用得到的话可以直接拿走：
这些资料，对于【软件测试】的朋友来说应该是最全面最完整的备战仓库，这个仓库也陪伴上万个测试工程师们走过最艰难的路程，希望也能帮助到你!有需要的小伙伴可以点击下方小卡片领取