Scrum and XP in the smoke (password: u5i9)
Author: Henrik Kniberg
Summary: In this book, author Henrik Kniberg describes how he led a team of 40 people to implement Scrum over a year. They tried different team sizes (3-12 people), sprint lengths (2-6 weeks), and definitions of “complete”Ways, different backlog formats, various test strategies, multiple ways to synchronize across multiple Scrum teams. They’ve also tried XP practices — continuous integration, pair programming, test-driven development, and so on — and tried to combine XP with Scrum.
This book describes the working process of a successful agile team, with no theory, no citation, no footnotes, no nonsense. Readers can use it as an introductory guide to some basic practices to help the team implement correctly — but not imitate it, you need to understand your environment and then work on specific practices.Choose and create a process that belongs to you.
Exploratory testing (password: 8tge)
Author: Shi Liang
Introduction: the road of exploratory testing practice can be divided into 4 parts. Chapter 1 introduces the definition and theoretical basis of exploratory testing and answers common questions that testers are interested in. Chapters 2-7 introduce the specific techniques of exploratory testing, including thinking method, test design, test tools and test selfDynamic. The eighth to 12 chapters discuss how the test team implements and manages exploratory testing. The thirteenth chapter reviews the contents of the book and analyzes the key factors for the success of exploratory testing.
HTTPAuthoritative guide (Chinese version) (password: h41b)
Authors: David Gourley / Brian Totty
Summary: In this book, we try to sort out some interrelated and often misunderstood rules in HTTP, and write a series of chapters based on a variety of topics to introduce the various features of HTTP. Throughout the book, we explained in detail why HTTP did so.It’s not just about how it is done. Moreover, to save time in searching for references, we have also introduced important non-HTTP technologies that are necessary for many HTTP applications to work properly. In the appendix that is easy to use, you can find the head in alphabetical order.References (these heads form the basis of the most common HTTP text). We hope that this conceptual design will help readers to use HTTP.
This book is written for anyone who wants to understand HTTP and the underlying structure of Web. Software and hardware engineers can also use this book as a well-organized reference book for HTTP and related web technologies. System architects and network administrators can better understand how to design, implement and manage through this book.Miscellaneous network architecture. Performance engineers and analysts can benefit from the relevant sections of caching and performance optimization. Marketing and consulting experts can better understand the future of web technology by introducing concepts.
GoogleThe way of software testing (password: 4w88)
Summary: Google Software Testing tells you from an internal perspective how the world’s leading Internet companies are coping with the unique challenges of software testing in the 21st century. The way of Google software testing has caught the essence of Google testing and seized Google test.The essence of the most complex software of the times. Google software testing describes test solutions, reveals how test architectures are designed, implemented, and run, introduces the role of software testing engineers, explains the technical skills that technical testers should have, and describes the testing engineers in products.Responsibilities in the life cycle; interviews with engineers who have described test management and played an important role in Google’s test history or major products have benefited those who have tried to build a test process or team similar to Google.
Microsoft’s approach to software testing (password: ujff)
Summary: This book begins with familiarizing readers with Microsoft products, Microsoft engineers, Microsoft testers, the role of testing, and common practices in software engineering. The second part of the book discusses many testing practices and tools commonly used in Microsoft. The third part of the book discusses some tools and systems used in our work.. The last part of the book explores the future direction of testing and quality at Microsoft and how we intend to create the future.
Deep understanding of computer system (original book Second Edition) (password: 3b7s)
Summary: This book elaborates on the essential concepts of computer systems from a programmer’s perspective and shows how these concepts really affect the correctness, performance, and practicality of applications. The book consists of 12 chapters, including information representation and processing, machine-level representation of programs, processor architecture, optimizationProgram performance, memory hierarchy, links, exception control flow, virtual memory, system level I / O, network programming, concurrent programming, etc. The book provides a large number of examples and exercises, and some of the answers to help readers deepen the understanding of the concepts and knowledge described in the text.
The greatest advantage of this book is that it describes the implementation details of a computer system for programmers, helping them to construct a hierarchical computer system in the brain, from the lowest level of data representation in memory to the composition of pipelined instructions, to virtual memory, to compilation systems, to dynamic loading libraries, to the final user-mode applications.By understanding how the program is mapped to the system and how it is executed, readers can better understand why the program behaves like this and how inefficiency is caused.