Today, the editor finally told me what it was like. The next step was printing, and we finally saw the dawn of light.
This is the album art of the book that was edited and sent to me. I personally feel that the design is okay. I don't know what you think?
This is the cover:
This is the back cover:
Next we will introduce the author (that is, I:
The content of this book is described as follows:
This book is a book devoted to describing software performance testing. for readers who do not have much experience in performance testing, the author of this book tries to make it a manual or practice guide; for readers who have already conducted some performance tests and have some experience in performance testing, this book also hopes to provide some inspiration for them. The author of this book, in conjunction with his own experience in performance testing, elaborated on the concept of software performance testing and the organization of Performance Testing. At the same time, through a large number of well-selected instance descriptions throughout the book, the author expects this book to give each reader a performance test experience and experience.
Organizational structure of this book
This book introduces the entire process of software performance testing and provides a general process model.PtgmAnd shows how to apply the model to the software performance test with several valuable examples.
Introduction to each chapter
This book is divided into three parts. The previous article "Basic" describes the basic concepts in performance testing, the basic knowledge to be mastered, and the process model of performance testing. The next article "practice" uses4The actual performance test project that the author has experienced describes in detail the process of organizing, planning, designing, and result analysis for each performance test project; based on the author's experience, the "Appendix" provides some additional content that is very meaningful to readers.
The "Basic" includes the entire content from Chapter 1 to Chapter 5.
In chapter 1, this book first introduces some basic concepts related to software performance testing, focusing on software performance from different perspectives, this article gives a detailed explanation and discussion of common terms in software performance tests, such as concurrent users, response time, and throughput, some methods frequently used in software performance testing are briefly described.
The second chapter of this book provides the concept of the application field of software performance testing, the application scope of Software Performance Testing is divided into four different application fields: "Capability Verification", "planning capability", "performance tuning", and "Defect Repair. The concept of the field allows the performance testing engineers to better clarify the objectives of the performance testing project and determine the appropriate performance testing methods.
Chapter 3 and Chapter 4 discuss the principles of performance counters and performance testing tools. The third chapter focuses on the performance counters commonly used in operating systems, application servers, and database systems, and provides methods to analyze performance using performance counters. In chapter 4, this book uses the most common performance testing toolsLoadRunnerThis example shows the principle of the performance testing tool.
The fifth chapter is the key chapter of this book. This chapter introduces a general performance testing process model.PtgmAnd describes in detail the activities of each stage of the model. This chapter can serve as an effective reference for performance testing projects, helping readers fully understand how to plan and execute a performance testing project.
The "practice" is centered on four specific projects. The description of each project strictly followsPtgmThe model steps and activities are described. In addition, many techniques available in performance testing are introduced based on the characteristics of each case (for example, timestamp techniques, methods for processing verification codes,Sessionid).
The "Appendix" provides some valuable materials. Considering the different skills of the readers, the appendix A Unfamiliar LoadRunner Tool readers provide a concise but comprehensive LoadRunner Quick Start manual; Appendix B For more familiar LoadRunner In the appendix A Based on LoadRunner Is described in the Appendix. C Some valuable script and data processing techniques that may be used during performance testing are provided. D The template used in the performance test is provided.
Reading suggestions for this book
The "Basic" part of this book is an integral part of its own system. We recommend that you read it in sequence according to the organization of this article. Whether you are an experienced performance testing engineer or a testing engineer who is not familiar with performance testing, we recommend that you read this article carefully, in this way, we can establish a good foundation for an accurate understanding of other contents of this book. In particular, chapter 5 "Organization of performance testing" in the "Basic" section, because the content of this chapter is the basis of the case description section, therefore, we hope that the readers can carefully understand the content of this chapter and then compare it with the case description to achieve the greatest gains.
Introduction to "practice" 4 Specific cases, including cases 1 Is a relatively rough case, focusing on displaying the performance test process; 2 It focuses on the analysis and design of performance testing, and shows a large-scale performance testing case where no commercial testing tools are used for testing. 3 Integration LoadRunner Detailed Performance Test description; Case 4 It shows how to achieve the purpose of selection through performance testing. This article 4 The cases are independent of each other. Readers can read the cases in the arranged order or choose any cases of interest for reading.
The content of the "Appendix" can be used as a reference manual for readers. LoadRunner Readers can LoadRunner Use the appendix A Obtain LoadRunner Basic knowledge of tools; used LoadRunner For a period of time, you can directly B Understanding LoadRunner In addition, the performance test templates and scripts provided in this Article can directly play a role in your project.
Who should read this book?
This book is intended for testing engineers, test managers who are interested in performance testing, or other people who want to learn about performance testing. This book is especially suitable for the following types of readers:
n testing engineers who want to understand the specific methods and processes of software performance testing.
n you want to find a test Manager that can immediately guide the process of performance testing.
n A test engineer or test manager who has some experience in performance testing but wants to verify the correctness of his or her work methods.
n Performance Testing engineers who want to learn from others' experience.
n other people who want to fully understand Performance Testing.