LoadRunner's experience

Because the company wants to conduct stress tests on a project, it needs to use LoadRunner for Scenario Design. After studying LoadRunner for a day, I feel that testing is actually an art.
I think everyone knows about the basic usage. Here I will explain several problems that beginners often encounter:
I. Error 26630
Cause: this error is basically because when you enter the web application system, the server once again issues an authentication window, And the LoadRunner cannot capture this pop-up box, this error message is displayed.
Solution: If loadrunner9.0 + is used, after the script is recorded, another form is provided for you to enter the account, password, and domain name. In this case, you can enter the correct one, loadRunner automatically produces a code at the beginning
Web_set_user ("[domain_name] \ [acount]", "[Password]", "[IP]: [port]"):
For example, web_set_user ("sbit \ test85", lr_decrypt ("4ba87ac245d3cf3bbd6f"), "vsvr059163.sbit.sbdeve.com: 9000 ");
Note: lr_decrypt ("4ba87ac245d3cf3bbd6f") is the LoadRunner's encryption function.
Ii. Error 26377
There are many causes of this error. The most direct result is no match found for the requested parameter "XXXXX ". this means that no matching value is found for the correlated variable. In fact, no matching boundary result is obtained from the returned message.
Possible causes
1. A script error occurs because the script error does not match the value of 22,028 times twice. It may be excluded (but cannot be completely excluded. You need to carefully check the log analysis results returned here.
2. the parameter list error actually caused a script running error and did not return the correct page and result (it may not arrive at the page you imagined at all and jump to a certain place for special reasons)
3. If the server is overloaded and the correct webpage message is not returned within the specified time, the data cannot be found. (Do not repeatedly query or update the same entry)
4. web_set_max_html_param_len is too small. There is not enough space to store the returned packets, that is, the information you want is truncated somewhere because of insufficient storage space. Setting a larger value may solve the problem.
26377 this error is common, but there are many causes. You can provide more information to help you find the cause.
3. HTTP-500 Error
The cause of this error is as follows:
1. If the number of running users is too large, causing too much pressure on the server and the server cannot respond, an http500 error is reported. Reduce the number of users or scenario duration and solve the problem.

2. If the link is not associated, an http500 error is returned. Manually or automatically associated to solve the problem.

3. The page or image requested during recording. If the server cannot find the page during playback, an http500 error is reported. If the page does not matter, comment out the page in the script, the problem will be solved. For example, if you have a verification code

The test is blocked, but the request is submitted during recording, but no response is returned during playback.

4. If the parameter value is incorrect, an http500 error is returned. You can take the values in the parameter list to the actual application system for testing to eliminate the problem.

5. If the application server (such as Tomcat, websphere, and JBoss) is replaced or the recorded script is used for running, an http500 error may be reported. Because the processing mechanisms of various application servers are different and the recorded scripts are different, the solution is to record the script.

6. If Windows xp2 is incompatible with the ISS component, an http500 error may occur. After the ISS component is adjusted, the problem is solved.

7. If the system development program is written incorrectly, an http500 error is reported. For example, some pointer problems are not handled properly, and there are null pointers. Solve the problem after modifying the program.

In my summary, the most important thing is the data logic errors produced by form data, such as data uniqueness, empty records, and data verification failure, this is the reason I encountered when recording scripts.

Because we are about to develop new projects, we don't have much time to understand them. Finally, I lamented that the QA that programmers dislike most is actually your original motivation.