Insert a picture description here.
Foreword:
Software testing is accompanied by the production of software. In the early software development process, the software scale was very small and the degree of complexity was low. The software development process was chaotic and random, and the meaning of testing was relatively narrow. Developers equated testing with "debugging" with the purpose of correcting what is already known in the software. The failure of this part is often done by the developer himself.
There is very little investment in testing, and testing is too late. Testing is often done when the code is formed and the product is basically completed. By the early 1980s, the software and IT industries had entered a major development. Software tended to be large-scale and highly complex, and software quality became more and more important.
At this time, some basic theories and practical techniques of software testing began to take shape, and people began to design various processes and management methods for software development, and the way of software development gradually transitioned from a chaotic and disorderly development process to a structured development process. , Characterized by structured analysis and design, structured review, structured program design and structured testing.
People also incorporate the concept of "quality" into it. The definition of software testing has changed. Testing is not only a process of finding errors, but also takes testing as the main function of software quality assurance (SQA), including software quality evaluation. Bill Hetzel pointed out in the book "Complete Guide of Software Testing" (Complete Guide of Software Testing): "Testing is any kind of activity with the goal of evaluating a program or system attribute. Testing is a measurement of software quality." This definition has been so far. Still cited. Software developers and testers began to sit together to discuss software engineering and testing issues.
Body: Recommend a book list related to software testing today!
Software Testing Series Book List
Insert a picture here to describe the
software testing technical guide
This book introduces advanced software testing technology and testing concepts at home and abroad: including software testing theory, software quality, software testing process, software testing methods, software testing management, software testing tools, web project testing and API project testing, etc. The book covers basic and high-level software testing knowledge, and combined with the current job skills required by the market, it provides test examples with great reference value.
This book is a professional book in the field of software testing carefully created by all teachers of Tengshang Times Software Vocational Training School. It strives to enable more job seekers and readers to learn software testing related knowledge and find more ideal software testing jobs. post.
This book is suitable for technical personnel engaged in software testing and other professionals who wish to engage in software testing. It is also suitable for students and teachers in computer, software, automation and other related majors.
About the Author
Fu Yongwei, male, currently serves as CEO of Shenzhen Tensun Times Information Technology Co., Ltd., COO of Shenzhen Sunruida Information Technology Co., Ltd., Chief Marketing Consultant of Shenzhen Dahan Marketing, and principal of Kunming Tensun Times Vocational Training School.
The art of software testing
"Software Engineering Technology Series: The Art of Software Testing (Original Book 3rd Edition)" has been more than 30 years since the first edition was published. It is a classic work in the field of software testing. The book structure is clear, the explanation is lively and lively, and it shows concisely the tried-and-tested software testing methods and wisdom.
Software Engineering Technology Series: The Art of Software Testing (3rd Edition) starts with a self-evaluation test. Starting from the psychology and economics of software testing, it discusses code inspection, walkthrough and review, test case design, and module (unit ) Topics such as testing, system testing, and debugging, as well as advanced topics such as extreme testing and Internet application testing, fully demonstrate the author's software testing ideas. On the basis of the previous two editions, the third edition has been updated with new developments in software testing, covering usability testing, mobile application testing, and agile development testing.
"Software Engineering Technology Series: The Art of Software Testing (Original Book 3rd Edition)" is suitable for software developers, IT project managers and other related readers, and can also be used as a textbook or reference book for computer-related professional software testing courses in colleges and universities.
About the Author
Glenford J. Myers, a former senior researcher at the IBM Systems Research Institute, is also the founder and former CEO of RadiSys.
Tom Badgett, once in charge of large enterprise software development teams, has published more than 60 technical books on computer software and hardware, and he is also the technical editor of mainstream computer magazines such as PcJr and Digital News.
Corey Sandler, a pioneer in computer journalism, was responsible for the technical part of Gannett Newspapers and the Associated Press and later became the editor-in-chief of Pc Magazine. He is also a member of the founding team of editors of Digital News (a newspaper for DEC minicomputers). He has published more than 150 books, covering everything from computer to business and many other fields.
Google Software Testing Way
"Google Software Testing Way" tells you from an internal perspective how the world-renowned Internet company has dealt with the unique challenges of software testing in the 21st century. "Google Software Testing Way" captures the essence of Google's testing and the essence of Google's testing of complex software in this era.
"Google Software Testing Way" describes the test solution, reveals how the test architecture is designed, implemented and run, introduces the role of software test engineers; explains the technical skills that technical testers should have; explains how test engineers are Responsibilities in the product life cycle; talks about test management and interviews with engineers who have played an important role in Google’s testing history or major products. This is of great benefit to those who are trying to build a test process or team similar to Google.
Finally, "The Way of Google Software Testing" also introduced the author's insights on how Google testing continues to evolve, and some predictions on the testing direction of Google and the industry as a whole. I believe many readers will feel the insights and even be shocked. This book can be used as a guide for anyone engaged in software testing to reach their goals.
"Google Software Testing Way" is suitable for developers, testers, and test managers. It is also suitable for learning books for teachers and students of relevant majors in colleges and universities, as well as teaching materials for training schools.
About the Author
Whittaker (James Whittaker), Google’s engineering director, is responsible for testing some of Google’s products, including Chrome, Maps, and GoogleWebApp. Before joining Google, James worked at Microsoft and before that he was a university professor. James is well-known in the global testing field.
JasonArbon, a test engineer (TE) at Google, has participated in the testing of Google Desktop, Chrome and ChromeOS. At the same time, Jason is also the development leader of a series of open source testing tools and personalized experiments. Before joining Google, he worked at Microsoft.
Carollo (JeffCarollo), a test and development engineer (SET) at Google, has participated in the testing of GoogleVoice, toolbox, Chrome, and ChromeOS products. Jeff provides consulting services to many internal development teams at Google, helping them improve their initial code quality. In 2010, Jeff transferred to a software development engineer (SE) and led the development of Google+ API. Before joining Google, Jeff worked at Microsoft.
Interface automation test continuous integration
This book mainly explains related content such as interface automation testing and the use of interface testing tool Postman. Chapter 1 introduces the basic knowledge of interface testing, including interface testing background, interface basic knowledge, interface testing process, interface documentation system, etc.;
Chapters 2 to 5 introduce the basic usage and advanced usage of the Postman tool, including introduction to the Postman tool, basic Postman operations, Postman collection, and the application of Postman scripts, to help readers learn how to use this tool to complete interface testing;
Chapters 6-7 introduce the basic usage of tools such as Jenkins, GitHub and DingTalk, and how to use these tools to achieve interface test automation and continuous integration; Chapter 8 reviews the contents of the first 7 chapters through actual projects to help readers from the overall Get an in-depth understanding of the essence of continuous integration of interface automation testing.
Whether it is a test engineer, test manager, or other people interested in testing technology, you can learn related knowledge through this book.
I recommend a software testing exchange group, QQ: 642830685. The group will share software testing resources, test interview questions and industry information from time to time. Friends can actively exchange technology in the group.