Book Reviews: My Opinion on the surging practice of Software Performance Testing and Load Runner

Book Reviews: My Opinion on the surging practice of Software Performance Testing and Load Runner

 

I only share my opinion on the current software performance test. Do not speak on behalf of most people in the industry or on behalf of most people in the industry.

The current market for performance testing is seen by many people as a relatively high level test in the testing industry (many people think that the high level also includes: testers who have not written code have been sending white box tests. We will not talk about white boxes here .). We can see that in some training courses, performance testing is a major concern.

Not everyone wishes to push it to this level because Performance Testing involves a lot of content. It will take some effort to enter this field. Most of the time, we can choose a related item, learn it, and then check what we need in this field after a while. Select another method.

To address this book, I would like to raise my own ideas:

 

1, Basic

In the book, the concept of performance testing is not very vague, but only a few common performance strategies are written, which is also a concern for beginners. The explanation is also approachable. I think many of the current performance testing concepts are repeated and cool. After talking about it for a long time, people cannot grasp the key points. It makes beginners confused.

The basic usage also involves the use of features with extremely high frequency. In fact, when we first came into contact with LR, we did not get much. More and more details will be considered only after you have a certain understanding of LR. I remember that when I first started learning LR, I thought it was too functional. I don't know how to set this part. Now I think I have learned more about it, and I think there are not many things to set up. The main reason is that the thinking is in place. Then it is easier to set anything. It is gratifying that the author has added some of his own experiences in the writing process. Some common problems are described. Instead of writing it again in the LR Manual (it cannot be ruled out that someone is doing this ). I always think that books with high practicability are worth pushing.

It seems that people think they are doing advertising;

In the basic section, I think it is not clear in some places. Let's say: When do we need to set the time for thinking? If you know what you want, you must know what you want. Here, the author only talks about other operations and the effect after the operation. In fact, this is not important, because it is also said in the help. I will not repeat other places.

The internal content of the basic part is not perfect. It can be based on the length or the publishing house. I am satisfied with the thickness of this directory and book. Like the installation of the Windows version, the next method should be known for all software installed on Windows, while the installation of the UNIX version is troublesome. This part of operational skills is not enough space. Some internal users can summarize their own ideas without referring to the Help content.

2, Practice

It is a good thing for the author to add what he has written. For example, write a batch to implement a function. Our actual job is to, many of which are difficult to do. Such an instance gives us some ideas. I think this is also the biggest highlight of this part.

The following section describes some problems. What should I do? I think there are both comments. From my point of view, I think this part is not important. Maybe it's because I have more forums. I felt like I was on the Forum again. But these are very practical for people who are new to LR. You don't need to search the Internet, and you won't go to the Forum to ask such a simple question, which leads to a group of people watching and not replying. I think this part is not enough. At the end of the LR help, there is also such a piece of information. I have read it carefully. It's really up to me for a long time.

3, Improvement

I personally think that the most important part is the experience of the author. Clearly describe the problem from start to end. Let the readers have a general concept. In the case section, I am not very convenient to evaluate it. Do not write it.

The interview later will be of some significance to some colleagues who are looking for a job in this industry. However, the content needs to be increased. From the perspective of the interviewer, it is really difficult to cover the interview questions. I have never thought about any questions I may ask during the interview. Unless there are some inherent problems.

 

In general, the value of reading should be determined by the positioning of books. As far as I know, people mail still hopes to include more performance testing groups. We also know that in the performance industry, the performance is still relatively small. Many people are in the phase of contact and learning, so this book can provide guidance to this group of people.

Some tips: to learn performance testing, you should still put your mind on it and do not look up on performance testing. Not that unattainable. We just need to spend more sweat. The most important thing for us to do is to have thinking. The thinking of performance testing is different from that of Function Testing. So we need to study the details. If you think that a job is just a job and you don't want to do it as well, you can just take a look. If you still have some fantasies and want to do well, you can work hard.

 

Details determine not only success or failure, but also your life.