The test staff must read the classic books

Software Testing: Experience and lesson: I recommend this book if I only get a referral. The book is made up of a lot of seemingly scattered little bits of knowledge, but Abas. People who have really done the test for 2 years, pick it up, each with their own work to do the contrast, will have resonance or "so" feeling. The more work experience, the deeper the experience, is a often new, and can always guide your book. In a sense, it teaches testers that "speculative thinking" is the most important asset.

Effective software testing: With the "Software testing, experience and lesson" is a part of the actual combat very strong summary of books, I think can also be included in the classics. Recommended reading when the work with their own one to do a comparison, it will certainly have a deep experience. (Some of the ideas inside may not agree with you, but it is a good thing to promote your thinking.) BTW, I like the checklist type of book very much. A long chewing, taste very good.

Software Testing Basics Tutorial: If you are not in the deep, want to fill in the most basic test theory. This book is undoubtedly quite a suitable textbook. Read a lot of books, ISTQB series is also the most systematic, the content is one of the best books.

Advanced Software Testing: Advanced software test analyst, advanced Software testing: Senior Software Test Manager These two books are ISTQB advanced certified training materials. If you do the test work for more than 3 years, you can buy 2 to see, a lot of things are very practical. If you see no sense, you can put it, work for a few years to see. If you've been improving over the years, you'll have to look at it. The inside of the thing is not all right, is not necessarily full of practical, but when you can understand most of the content, and can be refined to use the bad to work, you can say, test I did well. This is a self-examination handbook.

Explore: My heart 14 years the best Test book, but also in recent years a rare test good books. The definition, role, limitations, and implementation methods of exploratory software testing in this book are the best I think. Even if you're not a pure ET, a lot of the content of this book can help you improve the quality of your tests directly. Highly recommended.

Software testing: University textbooks, this book is still, some of the content is a bit outdated, but now it is still a very good introductory book, worthy of the novice to buy.

How to break software: The book I bought when I was in school was out of print, but there is an English electronic version on the Internet. Test Daniel James Wittaker's early works, you can read his later "exploratory software testing" and "Google testing the road." These books adhering to the usual self-made system of methods, abandoned the upper level, play the system of these roads, how to make the team better test how to come. There are a lot of classic cases in the three books, and there are a lot of simple and straightforward ways to get it right (you can try it quickly). However, be aware that the team that can do the testing as he says is a deep-rooted group of engineers with both Google and Microsoft, and do not worship blindly, according to their own team's ability to choose to adopt. If your leader reads it and thinks your company can do it, be sure to read this book and tell him that it really can be used and that it really needs to be postponed.

Continuous delivery: A systematic approach to the release of reliable software: the concept of continuous integration and continuous delivery is increasingly being embraced by various development teams, and good testing is an important cornerstone for continuous delivery that can be truly realized, a knowledge that every tester should have (at least conceptually, and capable of doing your part), This book is very informative, for usually only to do system testing students may be difficult to understand, but suggested to chew, slowly digest the inside of some knowledge, in the process of reading more with developers, SQA, product personnel, operation and maintenance personnel exchange.

Instantiation requirements: How the team delivers the right software: Each tester deserves a read (should be recommended for all members of the team), and you will definitely be bright and say: Great! That's the way to do it! The highest state of the book is an ideal "live Document System", in fact it is difficult to fully achieve, but in the inside of each part of the implementation of the test will improve the effect of a part, the team will be a little farther from failure.

Scrum essentials: In recent years, the domestic team has been doing agile transformation. So many testers experience the work of an agile team. The impact of agile implementation to software personnel is still very large, we also heard a variety of voices in the process. The scrum element tells a lot of small stories about how agile teams work, which is very practical, and testers are worth reading. If you practical kanban agile way, actually also has no relationship, read the same benefit. In addition, "Agile Software Testing" This book is also good, is reading very tired. If you are troubled by the agile transition, reading these two books can be a great help. Still, there are a lot of suggestions in these two books that are not absolutely correct, or that may not be suitable for your team to have a deep understanding of your team and then choose carefully.

The little black Books on test design: A book written by a veteran test engineer for free test designs, which he says is not a test design in our traditional sense, but a new methodology. In his eyes, the test design is not a static process, but a dynamic iterative process. READ carefully and you will reap great gains. Most worth mentioning is that the book quoted a lot of material, these materials are the essence of the essence, in a sense, the index of those materials accounted for half of the value of the book.

Software Testing: A book that has recently felt very good. Written by Shian, Microsoft's senior Test engineer, the few good books written by the Chinese. The greatest value of the book is that the author summarizes a large number of industry-tested cattle systems and methodologies, combined with practical examples of work to explain. In-depth study, the improvement of testing ability will be a great help, vision can also be greatly expanded. It is advisable to compare your work with the one described in the book when reading.

Software Requirements Best Practices: Testers should also look at the requirements related to the book, after reading we can know: how to get the needs in the right way, analyze requirements, describe requirements, maintenance requirements. This is actually a powerful weapon for testers.

Want to be on the level? What are the consequences of a demand-driven process from an organizational level? You need to crush the way of the comrades in the way, recommend this book to you: "Demand Engineering: Basic principles and technology." The Germans wrote, absolutely strategically advantageous position. In fact inside the method is very thick, not all adopt, but inside of modelling way and a lot of knowledge point very inspiring person.

Performance test:

Application performance Testing The art of software performance testing process analysis and Case analysis: These two books, a foreigner wrote, one is a Chinese reading. It mainly tells you how the performance test is done, why it is done, and the criteria, and there are good cases. If you really do performance testing, the recommendation must read these two, because this is in the methodology of things, no methodological guidance, you do not know how to model, how to design the scene, how to judge the results of the test. These two out of the domestic many "LoadRunner XXX" a lump of books 100 street. Learning LoadRunner actually looking at its official documents is enough. However, you are really small white, a little foundation is not, may wish to find this online evaluation of the relatively high "LoadRunner xxx" series of books to read, can help to quickly get started, experience how to operate, but the value is limited to this.

If you do a better performance test, you can actually look at related development books, such as architecture-related books, database management, tuning, JVM tuning, Web server management, tuning, high-performance programming, tuning excellence. The deeper you understand the analyte, the better the performance test can be. This is a book that can be searched by the keyword itself.

Security testing:

Penetration Testing Practice Guide: The best penetration Test primer, also a directory, can be opened by IT security testing door.

Automated testing:

There is no particularly good book, if not recommended, recommended: "Automated testing best practices" This is a case teaching book. There are dozens of examples, half of which I think is of great reference value. Automation to do well I think there must be at least 4 points: the right technology, the right strategy, the right team, the right time. Technology is only one-fourth successful in automating implementation. The book tells a lot of things outside of technology. Really do automated implementation of the students read it will certainly have a lot of feelings. If it is a beginner, it is recommended that you buy it, go through one or two failed projects (no very good engineer band, no good team, usually the first implementation is definitely a failure) and then read it backwards. In addition, there are several chapters in the beauty of testing that are related to automated testing and are worth seeing.

Also want to say, do not equate automation with QTP this thing. Unless your unit explicitly uses QTP, otherwise definitely do not buy QTP book to see, this thing is basically already the outdated, do not get a scam. In my eyes, the three most common testing frameworks that are worth learning are "Junit", "Cucumber", "robotframeork". You can learn a lot from the concept of framework testing and extrapolate. Specific test frameworks are recommended to be learned from selenium. Their best way to learn is to bubble forum, bubble official website, bubble Mail group, bubble domestic community, more people know the relevant person, do their own hands.

Other:

Cloud Service Testing: If you are interested in new technology, try buying one. Looks very tall on, after reading you will find: Oh, so. Old bottle of new wine. The good thing about this book is that it teaches you the methodology. You can replace the book's cloud service with the now more popular "Big Data", "mobile testing". After the change, you find, how the measurement is essentially the same, the difference is: The analyte has changed, familiar with your analyte, and set up a test system for the characteristics of the analyte is OK. Of course, you need to learn the relevant techniques of the analyte in order to complete the work, especially the test-related techniques. This is a lot of specific books, what to test when to buy a good wind evaluation of the book. For example, search for "mobile testing":)

My main job is to test the backend system, which is not very deep in many other areas. If there is a good book in a specific area, please follow the thread reply, share it with you.

Special spit groove, do not buy: "Test anti-mode: Effective evasion of the common 92 kinds of test traps" (Chinese version), the English version is still very good. Just translation of quite rubbish, basically is Jinshan quickly translated directly after the level of publishing, ruined a good book.

The last word is: reading and work are mutually reinforcing. Don't trust the book too much, it won't solve the problem in many cases. But the best part of the book is to enlighten you.

The test staff must read the classic books