Shulou(Shulou.com)06/03 Report--

The Soul of Software testing: core Test Design (2nd Edition) (mastering the core competence to become an irreplaceable testing elite)

By Xiao Liqiong

ISBN 978-7-121-19677-5

Published May 2013

Price: 59.00 yuan

356 pages

16 karat

Editor's recommendation

The reason why this book is jointly recommended by the technical authorities in the digital testing industry is that it clings to the life door of the testing work and focuses on the test design, and it is the only professional work on this topic at home and abroad. In addition to detailed theoretical analysis and technical details, there are some viewpoints worthy of attention and consideration by readers who have been or are determined to take this as their career, as excerpts are as follows.

(1) looking for a Bug is like digging a landmine. You have to be careful with every step, otherwise an bug will slip away under your nose if you are not careful.

(2) believe in yourself, Bug is endless, Bug is not gone, but I haven't found it for the time being.

(3) hold on! Serious incidental Bug should be paid attention to.

(4) not all Bug can be solved or need to be solved. The test should be persistent and willing to give up.

Content summary

With test design as the main line, this book first introduces the development and changes of the software testing industry over the past decade-now, software testing has been paid more and more attention by the world, showing the clues of the sunrise industry. How to grasp the testing technology, do the testing work thoroughly, and become a leader in the testing industry, is also a topic of concern to many readers. The book then defines the goal of testing and introduces all aspects of test design, including test architecture design, test requirements analysis and test strategy formulation, test scheme design, use case design, test execution process design, test output management design, test process control design and so on. Finally, the author extends the concept of chasing soft testing, which aims to help readers understand and watch the test on top of the testing work, how to surpass themselves to carry out testing innovation, and provide guidance for finding a way of testing essence of their own.

This book is the crystallization of the author's testing experience and wisdom in the past 13 years. It is suitable for test engineers who have some understanding of software testing, especially those who have some practical testing experience. At the same time, this book can also be used as a reference textbook for universities and software testing professional training institutions, allowing students to learn theoretical knowledge, learn engineering practice cases in enterprises, and pertinently understand and grasp the core technology of testing. In order to enhance their employment competitiveness.

Catalogue

Chapter 1 Software testing in Chaoyang 1

1.1 about software testing 1

1.1.1 the span from one corner of the book to the corner of the book mountain 2

1.1.2 catching worms and digging gold mines 3

1.2 Bug is right around us 5

1.2.1 Hewlett-Packard 100 notebook software exposed serious vulnerabilities 6

1.2.2 the Olympic ticket sales system was forced to shut down 6

1.2.3 US Fmuri 22 cluster system is paralyzed, software quality threatens national security 7

1.3 grasp the test post 8

1.3.1 getting started with testing 9

1.3.2 Outstanding Test 11

1.3.3 Test of Excellence 13

1.4 brief test basics 14

1.4.1 basic concepts of software testing 14

1.4.2 basic purpose of software testing 15

1.4.3 Software testing strategy 15

1.4.4 Software testing methods 17

1.4.5 Software testing process 18

Chapter 2 find the core thinking and realm of Bug 20

2.1 preferred mode of thinking 20

2.1.1 reverse thinking 20

2.1.2 divergent thinking 23

2.2 the first realm of testing: turning around Bug 26

2.2.1 go to a tall building alone-discover Bug 29

2.2.2 pining away for Iraq-- locating Bug 31

2.2.3 looking back suddenly-shut down Bug 34

2.3The second realm of testing: standing on top of Bug 36

2.3.1 the value of testing is more than just discovering Bug 37

2.3.2 tested service chain 42

2.4 the third realm of testing: challenge Zero defect 43

2.4.1 Prevention and blocking of defects 44

2.4.2 "zero defect" culture 46

2.4.3 misunderstandings after "zero defect" 47

Chapter 3 Test Design Landscape 48

3.1 look at the design 49

3.2 interpretation of test design 50

3.3 Invisible baton in test management: design of test organization patterns 53

3.3.1 Development-centered organizational model 54

3.3.2 organizational model with project manager as the core 56

3.3.3 Independent test organization model 58

3.4 A powerful weapon to improve testing efficiency: the design of the test process 59

3.4.1 understanding the testing process 60

3.4.2 keep everyone busy 61

3.4.3 the software runs like a snail crawling 64

3.5 good steel is used on the blade: suitable design for the application of testing technology 65

3.5.1 the heartbeat of communications is pounding 65

3.5.2 solve the riddle of use case failure 67

Chapter 4 Design of Test Architecture 70

4.1 think about the test architecture 70

4.1.1 Cognitive Test Framework 70

4.1.2 Test architecture design is not only technically 73

4.2 Let every tester see Hope 73

4.2.1 Review and reflection on Microsoft's testing career Development Route Design 74

4.2.2 suitable test technology development echelon channel 79

4.2.3 the appropriate test management direction of the architecture is on track 81

4.3 × × navigational Chief Helmsman-Design of the Business Test Architecture 83

4.4 the cornerstone of test construction-- the design of test framework 85

4.4.1 Photo frame and Test Framework 85

4.4.2 abstracting into concrete-Test Framework content 86

4.4.3 Breakthrough starting point-the method of building a testing framework 89

Chapter 5 Test requirements Analysis and Test Strategy Development 92

5.1 start with the test requirements 92

5.1.1 Multi-pronged traceability requirements 93

5.1.2 consider testability requirements 95

5.2 identify the true face of Lushan-Analysis requirements 98

5.2.1 Shortcut to quickly understand requirements: requirements announcement 98

5.2.2 the definition of requirements can also be wrong, not a lie 99

5.2.3 not to be ignored: extract test requirements 101 from design requirements

5.3 determine the top-level directivity test category 104

5.4 sermon-deployment of test strategy 107

5.5 tailoring and rational application of testing technology 109

5.5.1 Black box testing is not equal to manual testing 109

5.5.2 appropriate use of white box test 110

5.5.3 flexible use of gray box testing 111

5.5.4 partial automated testing 114

5.5.5 focus on special test 115

5.6 Test Planning and tracking Mechanism 117

5.7 other elements to be considered in the testing strategy 119

Chapter 6 focuses on the design of the test scheme 121

6.1 understand the design of the test scheme 121

6.1.1 questions and cognitive processes 121

6.1.2 importance of test scheme design 123

6.1.3 grasp the core-- the three steps of test scheme design 125

6.2 Innovation Paradise: multi-channel Test and Analysis method 126

6.3 three-tier architecture pattern analysis 128

6.3.1 principles of three-tier architecture pattern analysis 128

6.3.2 Application case 129

6.4 Multi-tree node analysis 133

6.4.1 the principle of multi-tree node analysis 133

6.4.2 Application case 135

6.5 Business State change Analysis 138

6.5.1 principles of business state change analysis 138

6.5.2 Application case 139

6.6 Code change retroactive Analysis 143

6.6.1 principles of retrospective analysis of code changes 143

6.6.2 Application case 145

Chapter 7 talks about the design of use cases 147

7.1 missed a prompt interface, not only lost 1.58 million yuan 147,

7.2 use case design in adversity 149

7.3 Technical tackling: efficient use case Design method 152

7.3.1 implicit boundary 152

7.3.2 Classification 156

7.3.3 unconventional operation 161

7.3.4 backward method 163

7.3.5 Comprehensive strategy for use case design 166

7.4 correct understanding of the validity and invalidity of use cases 167

7.5 value of use cases 169

7.6 Design reusable use cases 171

7.7 use case refactoring 174

7.8 the birth of the use case design specification 177

Chapter 8 Test execution process Design 179

8.1 requirements Test 179

8.1.1 Test requirements in the internal audit of requirements 181

8.1.2 Test requirements in external audit 183

8.1.3 Test requirements in the test design process 183

8.1.4 requirements test checkpoint 184

8.1.5 several questions in requirements testing 187

8.2 build release Test 188

Nightmare 188 released in version 8.2.1

8.2.2 A brief discussion on smoke Test 190

Message transfer released in version 8.2.3 192

8.3 regression Test 194

8.3.1 determine the content of the regression 194

8.3.2 use case-based regression testing method 194

8.3.3 regression testing method based on Bug 198

8.4 Cross Test 199

8.4.1 Features of cross-testing 200

8.4.2 Cross Test Mode 202

8.4.3 further thinking after cross-testing 205

Chapter 9 Test output Management Design 206

9.1 Bug Management 206

9.1.1 Story of "Bug list" 208

9.1.2 selection of Bug management tools 209

9.1.3 Bug Lifecycle Design 210

9.1.4 the Power of constraints-- Bug Management Specification 214

9.1.5 Application of Bug Library 219

9.1.6 processing of non-reproducible Bug 222

9.2 use case Management 224

9.2.1 use case Management tool selection 224

9.2.2 Design of use case structures and elements 227

9.2.3 Design for use case maintenance 231

9.3 Test document template Design 232

9.3.1 Test Plan template Design 234

9.3.2 Test Scheme template Design 235

9.3.3 Test report template Design 236

9.4 Test Summary Management Design 239

9.4.1 benefits of writing a summary 239

9.4.2 Test work log 240

9.5 Test knowledge Base Design 242

9.5.1 precipitation test knowledge base 242

9.5.2 Management of test knowledge base 243

9.5.3 is there a discount for learning to apply? 245

Chapter 10 practical methods for controlling the testing process 246

10.1 grasp the starting point of testing work 246

10.1.1 when is appropriate for testers to invest in the project 246

10.1.2 Project Test kick-off meeting 249

10.2 Review of test design 251

10.2.1 three-level evaluation mechanism 252

10.2.2 the birth of self-examination checklist 253

10.2.3 Design Checklist-an effective tool for improving Design quality 254

10.3 Control 256 for test version

Version 10.3.1 releases Photo 257

Version 10.3.2 receive / stop Test guidelines 258

10.3.3 Test and version number 260

10.4 Test configuration Management 261

10.4.1 testing also requires "surveillance cameras" 261

10.4.2 Construction and Application of Test configuration 262

10.5 missed test analysis: booster 264 with improved test flow

10.5.1 definition of missed test and significance of missed test analysis 264

10.5.2 missed problem Collection 266

10.5.3 missed Test Analysis Plan 267

10.5.4 missed test analysis implementation 267

10.5.5 implementation tracking of missing measures 268

Chapter 11 the Story of Software quality and testing 270

11.1 several stories of software quality and testing 270

11.2 what is the software quality model? 272

11.2.1 Standard definition of software quality 272

11.2.2 testers talk about software quality 273

11.2.3 Software quality Model-- Engineering practical interpretation 274

11.2.4 further reflection on the quality model 281

11.3 purpose of the test 283

Chapter 12 Design of Test patterns 285

12.1 understand test pattern design 285

12.2 Test mode based on user ring 286

12.2.1 identify user 286

12.2.2 case 1: the machine produced failed to boot 287

12.2.3 case 2: are exhibitors really tired 288

12.2.4 case 3: do we really know users? 289

12.2.5 case 4: complaints about the use of clothing 290

12.3 process-based test mode 291

12.3.1 case 1: the software is abnormal without any changes. 292

12.3.2 case 2: can't afford to hurt, the disaster caused by automatic construction 293

12.4 separate mode of test designer and test executive 294

12.4.1 case 1: test time has been increased by 295

12.4.2 case 2: recruitment intern execution use case 296

12.5 the combination mode of the excellent test team 300

12.5.1 case 1: test workload Assessment 300

12.5.2 case 2: story of testing requirements implementation 302

12.5.3 case 3: the Story of two slow 304

Chapter 13 chasing the concept of soft testing 307

13.1 develop new thinking of test management: test environment innovation 308

13.2 imagine: the development path of the test team 310

13.2.1 the era of wandering soldiers 311

13.2.2 Test guerrillas 312

13.2.3 Test Tribe 314

13.2.4 testing Division 317

13.3 Test design concept is supreme 318

13.4 Challenge testing new technologies 320

13.5 testing is indispensable "one leg" 322

13.6 Test Road to "Rome" 323

13.6.1 identify yourself-heroes don't ask provenance 324

13.6.2 choose a test that suits you. 325

Appendix An interpretation of professional terms 330

Appendix B Bibliography and Resources 335

Wonderful excerpt

Reprint preface

The Soul of soft Test was first published in February 2011. at the beginning, because the keyword "software testing" was not reflected in the title of the book, it adopted the colloquial "soft test" that is common at work. I was very worried about the impact on the market and whether it was acceptable to readers. However, in the more than a year since its launch, I have received book reviews from many readers, such as http://www.360buy.com/, http://www.dangdang.com/, China Interactive Publishing Network (http://product.china-pub.com), or e-mail feedback and interactions on Weibo, and some even post their comments online to share with each other. What moved me most was a test manager from a famous communications company in Nanjing, who communicated with me on many details in the book, saying that they were using the "Soul of soft Test" as a material to organize all the testers of the company to study and communicate together. For readers' letters or Wechat, I am basically a must. Perhaps because of the love of friends in the industry, a year later, I was glad to receive the news that the publisher could republish the book. On the one hand, I feel that I finally have the opportunity to correct the omissions in the original book; on the other hand, what is more important is that during the sales process of nearly a year, the last edition received feedback and suggestions from many readers all over the country. It makes me feel the enthusiasm of my friends in the testing world. Testing jobs have spread all over the country. a few years ago, they only appeared in first-and second-tier cities, while there are also software testing jobs in third-tier or developing marginal cities. It is their enthusiasm and the application of the contents of this book in my own work that promote me to keep learning and thinking, correct the existing problems, and implement the opinions or suggestions they have fed back to me, resulting in the second edition of the Soul of soft Test.

The changes to the second edition are mainly as follows.

The main contents are as follows: (1) two new chapters are added, namely: chapter 11 "the Story of Software quality and testing" and Chapter 12 "Design of Test patterns".

(2) due to the addition of two new chapters, in order to ensure the orderly convergence of the content, the original chapter 12 "chasing the concept of soft testing" was changed to Chapter 13 of the second edition.

(3) in order to facilitate readers to quickly grasp the main points when reading, highlight the important sentences of each chapter in the book (in bold).

(4) correct the mistakes and omissions in the first edition.

Xiao Liqiong

December 2012

Recommended order

Mr. Xiao works in Shenzhen and I work in Hefei. We are far apart, but we know each other because of our peers. More precisely, because of my "full Software testing", this book has become a link for us to get to know each other. In April 2008, Mr. Xiao bought this book and communicated with me about the problems in the book. Gradually we became familiar with it and became friends. So, when she started writing a book, she naturally thought of me, and I gladly accepted the invitation to write a preface to her new book.

Mr. Xiao worked in the testing field three years earlier than I did, and now he has worked hard in the testing field for 13 years. He can be said to be the veteran of domestic software testing. He has witnessed the development of domestic software testing from scratch, from a small workshop to a professional testing process, and he has also grown into a senior test engineer and test manager. She does love software testing, not only has been working in the testing field for more than a decade, but also thinks about the industry all the time, attends various software testing forums and other activities, and always wants to do something for the industry. To this end, Mr. Xiao began to plan to write a book on software testing practice three years ago to share his experience with you.

It is often said that test case design can best reflect the level of test engineers in software testing. If the testers do not understand the requirements enough, the designed test cases may not be correct, and the coverage of the designed test cases will not be complete; if the testers cannot grasp the technical implementation of the product, they will not be able to design targeted and efficient test cases; if the testers do not have a deep grasp of test methods and techniques, they will not know where to start to design test cases. If you do a good job of test design, the work of test execution is relatively easy. Only by designing the test cases correctly and comprehensively can we ensure that the test execution is correct, effective and complete, and finally ensure that the released products reach the required quality. Test planning and test execution are important, but test design is the core of testing work. This book is discussed around test design, but it is not limited to test case design, from test management design, process design, test organization structure design to test architecture design, test scheme design, test execution design and test output design, etc., so that the design is everywhere, showing us the wonderful realm of testing.

This book is the crystallization of the author's more than ten years of testing work, which can be witnessed by many examples in the book. In almost every section, there is an example, which not only makes it easier for us to read, but also makes it easier to understand the practical methods or problem-solving ideas that the author wants to explain. The language of this book is easy to understand. I hope readers will gain happiness and knowledge in reading.

Finally, I believe that readers will benefit a lot from reading this book, and like the author, they will love testing more and work in the testing field for 10 or 20 years, bringing the testing level of our country to another brilliant future.

Zhu Shaomin

Senior Director of QA

Cisco-NetXun (China) Software Co., Ltd.

A brief introduction to the author

Xiao Liqiong, born in Pingyuan, Guangdong Province, graduated from Xi'an University of Electronic Science and Technology majoring in computer technology. She has worked in the field of software testing for more than 10 years and loves testing. Good at test design, process control and process management of embedded software. He has led the testing team as the leader of testing in Taiwan-funded, Hong Kong-funded and private enterprises. Now, as a senior test engineer and test technical manager, he works in Shenzhen Mindray Blood Cell Research and Development Center.

Media comment

It took me a day to read the book, and I remember that few of the test books that had been published were devoted to test design. What attracts me in this book is the author's novel design method and easy-to-understand explanation. Each principle is explained, and the process of reading is very comfortable, just like seeing the author's good intentions. I also see the author's very deep test design experience and rich practice. After reading, I have a lot of experience and feelings, but also have a lot of harvest. Test design, as the most important and key work link in software testing, directly determines the results of later testing quality. I believe this book will be of great help to the improvement of testing skills of test enthusiasts. I recommend the majority of test enthusiasts to read and learn carefully.

Wu Kaihua, Assistant General Manager of Internet testing Department and President of quality Management Channel Branch of Tencent Company

The author of this book is a software system testing expert who has deeply understood and understood the process of software testing in more than ten years of testing practice, and summed up the best practices to guide the testing process. For many test engineers, it is a practical software testing book that makes it easier for beginners to understand through vivid examples. This book is very helpful for understanding software testing methods and processes.

Yuan Juan, Test Manager of Ultrasonic Software Department of Shenzhen Mairui Biomedical Electronics Co., Ltd.

Test design is the creative work of software testing activities and the technical guarantee to improve the effectiveness and efficiency of test execution. With the development of software testing industry in China, there are more and more books on software testing, but there are few books focusing on software test design technology. The publication of this book can fill the gap in this aspect. This book comprehensively discusses all aspects of test design, as well as the corresponding design technology, the combination of theory and practice, supplemented by typical test case analysis. Whether you are a software test architect, test engineer, test manager, or project manager, you can benefit from the book.

-- Cui Qiliang, senior expert of CSTQB, training director of Beijing Yuda Global Technology Co., Ltd.

Test design is the combat idea of our testers, which affects the quality of testing work together with testing tools. In the environment where test tools and automated test books are dominant, such a book describing test design can help testers gain knowledge and experience in the field of test design. This book illustrates the test design techniques mentioned through full and accurate practical cases, which is helpful for readers to easily understand the test design ideas and methods shared in the book, and is easy to apply to their own practice. If you are a test manager, the test management experience in this book can make you take fewer detours and walk on the right path; if you are a test engineer, the practical experience in this book can broaden your testing horizons and improve your testing professional ability!

Dong Jie, author of the Essentials of Software testing

This book is informative, well-discussed, widely quoted, profound and simple, and can benefit both newcomers and experienced testers who are new to the testing industry.

Cai Weidong, author of books on software testing

This book is a summary of the author's working experience in the software testing industry for many years, and systematically and comprehensively reveals the essence of software testing and the whole process of software testing. It can be regarded as a good book that can lead testers to enter the testing field and carry out testing work correctly.

Chen Nengji, TIB Automated Test Studio (http://www.cnblogs.com/testware)

Preface

As early as 1997, like many friends in the testing industry, they took up the post of software testing vaguely when they didn't know what software testing was about. Looking back, I never thought that testing would become an industry, and I never thought that I would be able to stay in this job for so long in my career. It is also very lucky to have the opportunity to witness changes in some aspects of the industry, such as testing professional books, from no professional books to a dazzling array of books. At the same time, it is also moved by many people and things in this industry, such as the emergence of a number of domestic testing experts in recent years, who dedicate their practical experience, whether through the publication of professional books or the establishment of personal blogs on the Internet. all brimming with love for testing. At the same time, in recent years, with the rapid development of the domestic software information industry, a number of companies or training institutions engaged in the software testing service industry have emerged, which makes the testing industry form quietly to make people feel that there is a scene of vitality and vitality everywhere. The prospect is infinitely bright.

There is a Guan Shanyue gallery in Shenzhen. On weekends, he often goes to an art exhibition with family or friends. The paintings on display are by Guan Shanyue, a master of traditional Chinese painting, as well as by other painters at home and abroad. Every time I come back from an art exhibition, I have some feelings. Software testing is also an art, a very beautiful art, but its expression is shown in Bug. As early as 25 years ago, G. J. Myers, an American software testing master, mentioned this point in his classic book the Art of Software testing. In view of the development of the domestic testing field in recent years, as well as some impetuous atmosphere and misunderstandings existing at present, as a person who has been working in testing for more than a decade, can I also do something? for example, wouldn't it be a good thing to share the experience and experience of these years with readers, so that newcomers can take fewer detours?

With an idea, it is not easy to turn it into a reality. At first, I thought it was very simple, thinking that I had accumulated enough material, and then I sorted out the material to become a book. As most of the professional books usually read are textbooks, a remarkable feature of this kind of books is that there are many concepts, the theoretical flavor is too strong, there is some distance from engineering practice, and often reading will make people doze off. But on the contrary, the novel books with ups and downs of the storyline often make us burn the midnight oil. So the performance style of the book wants to be different from the conventional break, and then in the following sample chapter will use the fictional style to talk about the concept of software testing, test design concept and so on. But in this way, the rigor of the core of the testing technology can not be reflected, and later, after repeated discussion with the editor, it is always reader-centered. Through vivid actual cases, combined with easy-to-read and easy-to-remember charts to show the style of the book, so that readers can easily read without losing the rigor of mastering technology.

When the outline and sample chapter of the book were determined, the writing process began for a long time. Just like we usually do projects in the company, at first I made a beautiful writing plan, but in less than two weeks, the schedule deviated from the plan, and then it got worse and worse. This has something to do with the fact that the company is busy with work and has limited (or no) time to squeeze out part-time writing every day. Sometimes it is really too tired, not only physical strength, but also sometimes feel willing but insufficient, such as an hour originally planned to write about 1000 words, but often two hours later to figure it out. From the beginning of the accumulation of writing materials to the completion of writing took nearly 3 years, I feel that it is quite a long time. Also want to back down many times, but have signed a contract with the publishing house, due to submit manuscripts, integrity is very important, with pressure, there will be motivation. I remember that in the middle of writing, I went to Wuhan for campus recruitment, so I had to take the manuscript and continue to write whenever I was free. There are still many things that happen in the whole writing process, whether setbacks or failures, it is a rare experience. By writing this book, I have the opportunity to learn a lot of new knowledge, and in the process of summary, I keep thinking. Testing is a deep knowledge, and there is still a long way to go to do it thoroughly.

The following is a brief introduction to the chapters of the book to help readers guide the reading.

The whole book focuses on test design and revolves around a process of test design.

The book is divided into 13 chapters.

Chapter 1 Software testing in Chaoyang Middle School

Against the background of the changes in professional books and network resources that have a special impact on the soft testing industry, this chapter will introduce the rapid development of the testing industry in the past decade. What does the soft testing work do and what is its core? With the vigorous development of the information industry, software has come to all aspects of our work and life, software is everywhere, it can not be perfect, Bug is everywhere. Accidents caused by software vulnerabilities or defects often occur. Software testing, which is the last hurdle of software quality, has been paid more and more attention by the industry. As a result, the testing industry has shown the clues of the sunrise industry. How to grasp the testing work and win a place in the testing industry? the last two sections of this chapter share some opinions on how to grasp the testing work at all levels, and at the same time introduce the essence of the basic knowledge of testing in a concentrated way, in order to guide the beginners.

Chapter 2: find the core thinking and realm of Bug

To promote the improvement of software quality by finding Bug is the most basic purpose of software testing. Around Bug, this chapter first introduces the value of reverse thinking and divergent thinking in finding Bug. Then it introduces the triple realm of the test, and the understanding of different states will have different behavior results. The first realm: revolve around Bug. Only by discovering Bug, assisting developers in analyzing problems, locating problems, and finally solving Bug, can we make a substantial contribution to quality. The second realm: stand on top of Bug. We can jump out of the small circle of testing software and broaden our horizons of testing. The value of testing is not only to find Bug, it serves the entire product development chain, the success of the project can lead to the success of testing. The third realm: challenge zero defect. Bug is designed, and it never dies on its own. The pursuit of zero defects is based on prevention, supplemented by testing and verification afterwards, and actively promote the design to be done as well as possible at once, which is the highest state of testing. Through the introduction of the triple realm of testing, readers can have a more comprehensive and reasonable understanding of the value of testing.

Chapter 3 Test Design Landscape

This chapter first makes a textual analysis of the names of design and test design, hoping to help readers better understand the essential meaning of test design. Then it takes the management design of the test organization pattern, the design of the test process and the application design of the test technology as the outline, combined with a case to describe how to apply the test, reflect what the test design is all about, and what is its important impact on the testing work. Through the introduction of this chapter, I hope to help readers understand the core idea of "test design is a process".

Chapter 4 Design of Test Architecture

This chapter starts with thinking about the testing architecture, discusses what the testing architecture is and what aspects it contains, and then analyzes the topic that testers are most concerned about-- the design of the testing career development path. so that readers in different related testing fields can find their own position and direction of effort. Next, this chapter puts forward an architecture design model, and then around this model, it describes the abstract concept of "test framework" at the bottom of the model, combined with the familiar photo frame in daily life as an example. finally, the content of the framework and its design method are introduced.

Chapter 5 Test requirements Analysis and Test Strategy formulation

This chapter starts with the introduction of test requirements, sharing with readers how to go beyond the requirements documents, collect more and more comprehensive requirements, and then how to analyze these requirements, especially the identification of some implicit requirements, so as to extract directional top-level test objects. Then, in order to deploy the testing strategy for the extracted test objects, it focuses on the tailoring and reasonable application methods of various testing technologies, mainly black-box functional testing, appropriate white-box testing, flexible use of gray-box testing, and automated testing for some functions or modules. At the same time, we should focus on the special testing, in order to break through the testing mode of certain characteristics, and bring more contribution to the reliability and stability of the project software quality. The test plan and the tracking and control methods of the whole test process are also one of the main contents to be considered in the strategy, which are also introduced in this chapter. Finally, it introduces other factors that need to be considered in the testing strategy but are easy to be ignored.

Chapter 6 focuses on the design of the test scheme

First of all, this chapter reviews the different views and practices of the industry on test scheme design, and puts forward the importance of test scheme design through experienced examples. Then it gives a variety of test object analysis methods extracted from the best practice, including three-tier architecture pattern analysis, multi-tree node analysis, business state change analysis, code change retroactive analysis. For each method, first explain the principle, and then combined with the case, share with the reader how to apply in the specific work practice.

Chapter 7 talks about the design of use cases

This chapter first takes a missed quality accident as an example to illustrate the importance and significance of use case design, and then puts forward some solutions to how to design use cases without the basis of requirements and design documents when the development process is not standardized. I hope it will be of some help to the testers who are in this predicament. Then put forward several effective use case design methods, and combined with cases to describe how to apply, friends who want to improve the design of efficient use case methods can find what they want. With the method of use case design, we also need to have a correct understanding of use cases, including the correct understanding of effective and ineffective use cases, and the value that use cases bring to us. Use cases are the world in the mind of testers, just as code is the soul of developers. The reuse and refactoring of use cases are worth thinking about and will be shared with readers in this chapter. Finally, the design specification of the use case is introduced as the end of this chapter.

Chapter 8 Test execution process Design

The design of test scheme and use case belongs to the design of pure testing technology, but for the testing process of the whole project, technology alone is not enough, it needs to be matched with an appropriate testing process to plan when to do what and what requirements to achieve. Good planning can get twice the result with half the effort in the testing of the project. This chapter focuses on the design of the test process, combined with a case, introduces the test links of each stage design and its specific application.

Chapter 9 Design of Test output Management

Taking the test output as the core, this chapter introduces how to manage the test output in an effective way, make full use of the value of the test output, and improve the testing process, in order to improve the quality of software testing. Combined with the case, this chapter introduces the solving measures and the methods to improve the testing process.

Chapter 10 practical methods for controlling the testing process

The previous chapter describes how to do each link in the testing process, and how to manage what is done, involving the method of test design, the design of test execution process, and the management of different types of test output artifacts. The method, process and management form an orderly and perfect test link. However, are the test nodes interlocking with our expectations? After all, only when the quality of each node is guaranteed, can the end of the test link come to a successful full stop. This chapter introduces the method of how to control each node in the testing process with a case study.

Chapter 11 the Story of Software quality and testing

This chapter mainly focuses on the test design of software products in each link of the life cycle. Standing at a higher level of this line, this chapter systematically considers the relationship between quality and testing, including how testers view software quality, what are the quality attributes in the standardized software quality model, and what is the relationship between them and testing? what is the purpose of testing?

Chapter 12 Design of Test patterns

This chapter describes the design of the test pattern, how to improve the testing process through the change of the test pattern, and finally make the wall of software quality higher and stronger. The design of test patterns is not limited to technology-related test patterns, but is closely related to process management, personnel matching management, psychology and so on.

Chapter 13 pursues the concept of soft testing

This chapter communicates and shares with readers some important ideas about the work or development direction of testing friends, including test innovation, the supremacy of test design, the challenge of new testing technology, the way of testing, etc.

Common test methods and type explanations are attached at the end of this book.

Participating in this book are Xiao Liqiong, Zhang Taoqing, Lu Suzhen, Ma Xue, Jia Ruixia, Zheng Decai, Li Lixiang, Chen Dongyong, Huang Yuanhui and Wang Ting. Due to the limited level and time of the author, there will inevitably be some problems or errors in the book. Readers and colleagues from all walks of life are welcome to correct them, and contact the author: ch_testinfo@126.com.

When writing this thank-you speech, I thought it over and couldn't write it for a long time, as if there were a thousand words, but I didn't know where to start.

First of all, I am very grateful to my first reader, my family, who gave me great support throughout the writing process. As a result of part-time writing, the company's project tasks are tense, overtime is common, free time is very limited, often can not complete the writing schedule as planned. When I was in trouble, it was they who constantly encouraged and supported me, and finally fulfilled their wishes after repeated psychological challenges.

Secondly, when I first contacted the publishing house, I was repeatedly shut out because of the problem of method. It was teacher Cai Weidong who extended a warm helping hand. It was because of his guidance that I quickly found a partner-Zhang Chunyu, editor of Electronic Industry Publishing House. I would like to express my heartfelt thanks here!

Nearly a year's writing process has passed. As it is the first time to write a big book, Editor Zhang has spent a lot of time and effort to guide me throughout the writing process. I would like to apologize for some of my mistakes or deficiencies. But more is to thank him for his consistent support and strict requirements. In addition, in the self-examination stage after the completion of the book, I was lucky to get the guidance of teacher Zhu Shaomin, so that the quality of the book has been further improved. I would like to express my heartfelt thanks here.

And my good friend Lucy, who is my first professional and technical reader, has given me a lot of meaningful feedback. Although she has emigrated to Canada, she has been concerned about the progress of this book. Thank her for her great support.

Also because of writing books, I almost ignored my daughter for some time, which made me feel very guilty. The fourth grade was an important period of transition. I was always worried that her grades would decline without the tutoring that I should have done. Surprisingly, she improved in the end. I am gratified by the growing up of my daughter. Of course, this is still inseparable from the care, love and teaching of my family.

Finally, I would like to take this book as the most precious gift to my relatives, friends and colleagues who have been silently supporting me.

Xiao Liqiong

Shenzhen in July

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.