Only "a little bit", why do developers look up to you?

as everyone knows , Nowadays, whether large or medium-sized factories , Automated testing is basically standard , After all, it's like a double 11、618 The huge and complicated system in this activity , And multi terminal publishing 、 Many versions 、 Model release and other requirements , But only “ Write some automated scripts ” It's hard to be competent for . This can be seen in the recruitment requirements .

However , In reality, it is difficult to recruit a mature Automation Test Engineer .

Recently, I interviewed many test engineers from large factories ： Huawei 、 Wal-Mart 、 tencent 、 byte …… wait , I think it's stable every time , I think I have participated in automation testing in large factories , Actually, there are many Work 10 A test engineer in 2000 , Still doing functional testing , Or focus on functional testing .

Why is automation testing talent scarce ？ I summed up 3 spot ：

• The field of automated testing is limited to the use of tools and frameworks , Lack of overall cognition ;

• Do not have a deep understanding of automated test design , Some methods 、 Routine stays in conceptual understanding , You can't use it flexibly ;

• The value of testing is underestimated , Long term development is limited , Forced to roll in technical tools with developers .

Do the most cost-effective automated testing

Think about it first , We automated testing “ End point or value ” What is it? ？

• Is automation running ？ This requirement is too Elementary ;

• Is the leader satisfied ？ Sometimes because of a change of leadership , In the middle of the project ;

• yes 100% Automation ？ 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 , Completely subverted my cognition ——  The ultimate delivery value of an automated test project is the benefits it generates , That is, the investment return ratio ROI.

At first glance to , It's a little hard to understand , But think about it , Isn't that what happened .

For example , In the year-end report , use ROI Express performance in a way ：“ Boss , The automation test case I did , Last year was n A scenario uses , Run repeatedly x Time , Find out bug y individual , Save manual work z Man Month ”.

Isn't that intuitive ？ To be a master , We must see and solve more valuable problems , Be responsible for higher results .

Become a master of automated testing

Compared with 80% Well known to test engineers from “ codability → Tool capabilities → Architectural capability ” The cognitive route of , This new model , All of a sudden, it pierced the essence of the work of test experts —— Understand the business 、 Know technology 、 Understand Architecture , Not limited to tools and frameworks .

Compared with just talking about tools and frameworks on the market 、 The code and other materials like the operation manual are different , What attracts me most about the column , It's the author who created a lot 「 automated testing 」 Methodology that first appeared in the industry （ Let's talk about it in detail ）, Take you out of the level of tools and frameworks , Reexamine automated test design .

As discussed by the teacher and a classmate in the column ：

Now many testers learn the tools on the application layer , Rarely think from the bottom and Architecture

As a result, we can only write some automated scripts to run , But you can't understand the cause of the problem itself , Especially the performance problem , Many testers only know how to run under pressure , But I don't know the system , The Internet , The relationship between applications .

The column deals with measurement data analysis 、 Code logic and Job modeling , It also corresponds to the data in software development 、 Algorithm and modeling , He is still there. GitHub I created one on repo Put the overall code and related documents mentioned in the column , Convenient for everyone to operate .

Of course , although  80%  The content of is 「 cognition 」 The height of the top , But he will also list the mainstream tools and frameworks in the industry , As well as the selection strategy and landing practice , and Attach the list of full stack automated test tools . But this part only accounts for 20% , After all, these things can be found online .

Who is Baili ？

Actually , I've read hundreds of miles of articles before , Immediately attracted by his fresh angle , I can feel that he has a very thorough understanding of the testing position , It also comes from his unique experience ：

• Worked at Motorola 、 Oracle China , Successively served as test manager 、 Senior Development Manager 、 Test director and other positions

• Lead the team to design distributed automation framework Automation Center, Filled the Oracle 20 For many years, there has been a blank in the field of automatic testing of video conference system ;

• Qcon Lecturer at the global software development conference ;

In the daily test person's work , Can only touch “ To build the wheels ” Partial , Limited vision . And a combat expert like Baili , It can let you know the testing position from a higher level , This is the rarest .

Why is it worth recommending ？

One 、 Subversive cognition

Baili put forward many new methodologies in his column , And for the first time in the industry ：

• “ Microtest Job Model ”, In this Job In the model , No, TestSuite and TestCase The concept of , There is no dependency on specific tools and frameworks , It's oriented to test requirements and automated testing ROI Require design ; It can help you clarify the test scenario 、 workflow 、 Cases requiring code implementation, atoms, etc ;

• “ 3KU matrix ”, Used to comb UI test 、 Interface test and unit test the test capability of each section ;3KU Test pyramids , Layered testing each layer has its own concerns , But they can cooperate with each other as a whole 、 compensate ;

• Case study DM Analysis of the table , It can analyze the development cost and maintenance cost of different types of automated testing ;

• Tool four-dimensional maturity model , Used for frame type selection analysis and decision-making ;

• ......

These are just the tip of the iceberg , It has opened my eyes 、 I'm looking forward to it .

Two 、 Content systematization

Baili split the whole column into 4 Stages ：

The first module the first module Take you to re-examine the basic concept of automated testing , Master the quantitative thinking method of automatic test benefit —— Input output ratio ROI Model .

Second module Starting from an example of a ordering system , Upgrade from single application to micro service cluster , To observe changes in test requirements , Fully validate requirements through layer by layer testing .

Third module Deduce the model design together . Like the design pattern of development , Automated test design should also have its own methodology .

The fourth module Some measurement models and process examples driving improvement will be provided , Think about how to make a project always observable 、 controllable , Feedback . Ensure that the project is always on the predetermined track , Even if there is a deviation , It can also be found and corrected at the first time .

The following is the specific content of the column ：

Except for dry goods, of course , I also won benefits for you ！