Daily book -- analyze the pain points of software automation from simple to deep

Last year , When I revealed my idea of writing a book with some friends around me , Yes 3 A friend thought I was going to write travel notes , And at least 3 A more unreliable friend thinks I want to write a paragraph .

Although I have written travel notes , Also often send jokes , From time to time, I also share some of the hard work and fun of tutoring primary and middle school students in English and Chinese , however , These are just what I wrote casually , Not professional , There is no quality . What I'm good at , Write code , A little bit more specific , It's software automated testing , This is my craft for a living .

I'm a farmer , Master's degree in computer science , There are more than 15 Software industry in ( Especially in software automation testing ) Professional experience , I put my work experience 、 Lessons and thoughts are summed up , Wrote this book : 

《 Software automation test practice analysis _ be based on Python3 programing language 》

This is a book “ slow ” book .

Work 15 Since then , I haven't worked overtime , No Internet experience 996 The baptism of , It's basically not in “ tuyere “ Worked in the company , therefore , There is no big data in this book , No deep learning , There is no Internet of things , There is no blockchain , No bitcoin . Of course , No chance to be a pig taking off with the wind , I missed a lot of opportunities to get rich .

Such work experience , It's definitely not signed financially , however , Because I'm not in the tuyere industry , On the contrary, there is a craftsman atmosphere at work , Everyone is willing to spend time thinking and polishing , Solve or improve the problems encountered in the work one by one

The software industry has been developing rapidly , New frameworks and tools are emerging , The industry threshold has been continuously lowered , You can make a professional looking software program simply by putting it together , People have the illusion that software development is not difficult , Think 7 Sky master 21 It's a matter of fact 1 Take a big factory last month Offer It's entirely possible .

Different people have different definitions of beauty , The definition of difficulty is different , The definition of mastery is also different . One day you can learn to broadcast gymnastics , But I shouldn't be able to learn gymnastics ; You can learn to jump in three minutes , But you can't jump far .

Readily available software frameworks and tools , Let's put... In the blink of an eye 80% The problem is solved , however , Without solid basic skills , Lack of effective ideas to solve problems , The rest 20% The problem of , May never be sure .

This book , It's about software automated testing , But it doesn't directly give “ correct ” The ultimate solution ( I didn't myself ), It's a demonstration of how to start from the basics , Find the problem , Explore the direction , solve the problem , Iterations and improvements , A focus on “ fishing ”, Instead of “ fish ”. This is the proper idea of software testing , This idea is applicable to software testing , It also applies to software development ; For Software , It also applies to other things .

I have a point that I have said on many occasions ： For Engineers , Getting things done at a reasonable cost is the most important , As for whether technology is very low, Is the efficiency very low , Is the plan not tall enough , This is not the most important . Everyone has to go through the introductory stage , however , Even if it's just entry level , You can also use only the technical level to produce . For a rookie carpenter , When you can't make an exquisite mortise mechanism , Use density board and iron nails to knock out a bench that can sit , It is also commendable . For a cook , When the heat is not under control , Bite a steamed egg in the microwave , It doesn't mean TA There is no pursuit in cooking .

You don't have to learn Dugu Jiujian to kill people in the Jianghu ！

The contents of this book are organized according to the degree of difficulty 、 Advanced and high-level , Before and after content design , Echo each other , Readers can clearly see the process of polishing the details . Readers of different technical levels , Well designed content and examples can be seen at the corresponding level , Feasible engineering practice , And the skills and thinking direction needed to rise to a higher level .

Because of my ability , There are inevitably flaws and mistakes in the book , I'm sure readers will criticize and correct . In software development and testing , I'm still on the road myself , But I want to share my experiences and experiences along the way , Let there be more people on this road , Find more beauty , From this perspective , This is also a travel diary . 

 

Statement ： In this paper, from " Huazhang computer ” official account .