Reprint https://www.cnblogs.com/Invokerr/p/6894185.html
premise:
1) Download the Chrome browser and install it;
2) After installation, open vugen, and the browser can choose Chrome.
First of all, you have to install LR12, generally use LR12 to record, because it is not cracked, use LR11 to run concurrently.
The official documentation of LR12 supports chrome and Firefox, but there are still some problems in actual recording. There are two main problems found so far:
(1) LR records chrome, chrome pops up, but it is blank and stuck;
(2) After the recording is completed, the script is empty (not only chrome).
To solve this problem, you need an artifact: Fiddler.
The specific operation method is to open the fiddler, and then use the LR12 to record.
Then you will find a magical phenomenon. Chrome, which would have been stuck, can be recorded normally, and the scripts generated by recording various browsers or clients are not empty. At this time, both fiddler and LR12 will track the data, and if fiddler follows, LR will also be generated in the script.
In short, whenever you encounter various monster problems when recording with LR12 (the client or browser is stuck, the script cannot be generated after recording, etc.), you can basically solve it with fiddler recording. (At least the problems I encountered have been solved, LR11 is fine, it is seriously recommended to use 12 to record).
If there is still a problem and fiddler can't solve it, don't be afraid, we still have the ultimate trick: fiddler tracking, save it as a SAZ file, open it with the LR12 open solution option, and then there will be a touching scene: LR12 Automatically convert fiddler trace files into debuggable scripts. In this case, the script problem is solved, and you have to add the transaction by referring to it yourself.
It is estimated that some people have feedback, LR11 can not support it, 12 will be fine.
In fact, it is also possible to convert SAZ to script through programming (SAZ is a compressed package with a bunch of files in it), but it may be troublesome to analyze, but fortunately, HP solved it for us, so that when the function changes in the future, only If you need to grab the changed request, just switch to the script and replace it.