As we all know, automated testing is basically standard for both large and medium-sized factories nowadays . After all, there are huge and complicated systems in activities such as Double 11 and 618, as well as the needs of multi-terminal release, multi-version, model release, etc., but only "Write some automation scripts" is hard to do. This can be seen in the recruitment requirements.
However, the reality is that it is difficult to recruit a mature automation test engineer.
Recently, I have interviewed a lot of test engineers from big factories: Huawei, Wal-Mart, Tencent, Bytes, etc. Every time I thought it was stable, I thought that I should have participated in automated testing in big factories, but it is actually a lot of work. 10-year-old test engineer, still doing functional testing , or mainly functional testing.
Why is automation testing talent scarce? I made 3 points:
The field of automated testing is limited to the use of tools and frameworks, and there is a lack of overall awareness;
The understanding of automated test design is not in-depth, and some methods and routines remain in conceptual understanding and cannot be used flexibly;
Testing efforts are undervalued, long-term development is constrained, and developers are forced to involute technical tools.
Do the most cost-effective automated testing
Think about it first, what is the "end point or value" of our automated testing?
Is it running automatically? This requirement is too rudimentary;
Are the leaders satisfied? Sometimes because of a change of leadership, the project is halfway through;
Is it 100% automated? High automation does not necessarily lead to high quality;
It seems that it will be difficult to tell for a while, what is the value of automated testing. Until I saw the picture below, it completely subverted my perception - the ultimate delivery value of an automated test project is the benefit it produces, that is, the return on investment ratio ROI.
At first glance, it's a bit difficult to understand, but when you think about it, isn't that the case.
For example, in the year-end debrief report, express performance in terms of ROI : "Boss, the automated test cases I made were used in n scenarios last year, repeated x times, and found y bugs, saving manual work. Quantity z man-months".
Is it intuitive? To become a master, you must see and solve more valuable problems and be responsible for higher results.
Become a master of automated testing
Compared with the cognitive route of "code ability → tool ability → architecture ability" that 80% of test engineers are familiar with, this new model breaks through the essence of the work of test masters - to understand business, technology, Understand architecture, not limited to tools and frameworks.
Compared with only talking about tools, frameworks, codes and other information like operation manuals on the market, the column that attracts me the most is that the author has created a lot of "automated testing" methodology for the first time in the industry (detailed below), with You go beyond tools and frameworks and revisit automated test design.
As discussed by a teacher and a classmate in the column:
Now many testers are learning the tools above the application layer, and rarely think about problems from the bottom layer and architecture
As a result, they can only write some automated scripts to run, but they cannot understand the cause of the problem itself, especially the performance problem. Many testers only know the pressure to run, but do not know the relationship between the system, the network, and the application.
The column involves metric data analysis, code logic and job modeling, and also corresponds to data, algorithms and modeling in software development. He also created a repo on GitHub to put the overall code and related files mentioned in the column . It is convenient for everyone to operate.
Of course, although 80% of the content lies in the improvement of "cognition" , he will also list mainstream tools and frameworks in the industry, as well as selection strategies and implementation practices, and attach a list of full-stack automated testing tools . But this part only accounts for 20%, after all, these things can be found online.
Who is Baili?
In fact, I have read Baili's article before, and I was immediately attracted by his fresh perspective. I can feel that his understanding of the testing position is very thorough, which also stems from his unique experience:
Worked in Motorola, Oracle China, and served as test manager, senior development manager, test director and other positions
Led the team to design the distributed automation framework Automation Center, which filled the gap in the field of automation testing of video conferencing systems by Oracle for more than 20 years;
Lecturer at Qcon Global Software Development Conference;
In the daily work of testers, they can only touch the part of "building the wheel", and their field of vision is limited. And a practical expert like Baili can make you understand the test position from a higher level, which is the most rare.
Why is it worth recommending?
1. Subversion of cognition
Baili put forward a lot of new methodologies in the column, and this is the first time in the industry:
"Micro-testing Job Model", in this Job model, there is no concept of TestSuite and TestCase, and no dependencies on specific tools and frameworks, but is designed for testing requirements and automated testing ROI requirements; it can help you clarify test scenarios, Workflows, case atoms that require code implementation, etc.;
"3KU Matrix" is used to sort out the testing capabilities of each section of UI testing, interface testing and unit testing; 3KU testing pyramid, each layer of hierarchical testing has its own concerns, but can achieve mutual cooperation and compensation as a whole;
Case DM analysis table, which can analyze different types of automated test development costs and maintenance costs;
The four-dimensional maturity model of tools is used for framework selection analysis and decision-making;
......
These are just the tip of the iceberg, and they have opened my eyes to what I am looking forward to.
Second, the content system
Baili divided the entire column into 4 stages:
The first module takes you to re-examine the basic concepts of automated testing, and master the quantitative thinking method of automated testing benefits - the input-output ratio ROI model .
The second module starts from an example of a food ordering system, upgrades from a single application to a microservice cluster, observes the changes in test requirements, and comprehensively verifies the requirements through layer-by-layer testing.
The third module deduces the model design together. Like development design patterns, automated test design should also have its own methodology.
The fourth module will provide some measurement models and sample processes for driving improvement, and think about how to make a project always observable, controllable, and feedback. Ensure that the project is always advancing on the predetermined track, and even if there is a deviation, it can be found and corrected at the first time.
The following is the specific content of the column:
Of course, in addition to dry goods, I also won benefits for everyone! 