Fiddler Orchestra from installation to actual combat exercise

Last time I talked about the Fiddler Orchestra user guide, this time I will share my actual combat drills with you, without further ado, the steps are as follows:

1. According to the previous article "Fiddler Orchestra User Guide", the Fiddler Orchestra client and controller can only run on frameworks that support at least .NET Standard 2.0. My test machine here is a Windows system, with .NET Framework 4.7.1 (https://www.microsoft.com/net/download/Windows/run) installed. I won’t go into details about the installation, just follow the guide window to install it step by step. After installation, you will be prompted to restart the computer. In order to ensure the success of the subsequent test, restart immediately and drink a cup of tea.

If you want to learn the Fiddler packet capture tool, here I recommend a set of videos for you. This video can be said to be the No. 1 Fiddler packet capture tool tutorial on the Internet at station B. At the same time, the number of online users reaches 1,000, and there are notes available. Receipt and technical exchanges with various great gods : click on the card at the bottom of the article'

Play Fiddler packet capture with zero foundation and apply it in the field of testing! _哔哩哔哩_bilibili [Python interface automation test notes and video source code + WeChat: mashang-nn Remarks (555 at station b) can be collected for free, and three consecutive likes are the true love! 】, The number of video views is 1331, the number of bullet screens is 2, the number of likes is 4, the number of coins tossed is 2, the number of favorites is 20, and the number of reposts is 0. B station 555, related video: Play Fiddler's four major applications in the field of testing from 0! , 2023 the latest version of Jmeter performance test project practical explanation, from entry to proficiency in the actual combat tutorial worth 8888, Charles captures the actual combat application in the field of testing, mastered in one hour! , to build an api interface automation testing framework for station B, Postman interface testing is the most powerful tutorial interface project actual combat, you have everything you want, use Postman to easily play interface automation testing, WebSocket interface application scenarios and testing methods, learn performance testing in 15 days, popular Easy-to-understand detailed teaching, Jmeter performance test actual combat (cluster pressure test, full link pressure test, performance tuning, bottleneck analysis) mastered very quickly, just do it! , webdriver-helper automated testing actual combat, use Postman to easily play interface automated testing https://www.bilibili.com/video/BV14g4y1H7vv/?spm_id_from=333.999.0.0

2. Install .NET Core Runtime 2.0.6 and ASP.NET Core Runtime 2.0.6 (download address, still provide the address above)

ps: ASP.NET Core Runtime is not installed, and when starting the .NET Core Fiddler Orchestra Client in step 4, an error will be reported: An assembly specified in the application dependencies manifest (FiddlerOrchestra.Client.NetCore.deps.json) was not found…

3. Install the latest version of Fiddler on the test machine (must be the latest, the first version of 5.0 (December 2017) found a bug, and the problem was solved after the upgrade. Here I am: v5.0.20181.14850 for .NET 4.6 .1 Built: March 20, 2018). Then find the "Fiddler Orchestra Beta" tab. Download the Fiddler Orchestra client at the address provided below. After the download is complete, extract it to a directory.

4. Because .NET Core Fiddler Orchestra Client is an ordinary ASP .NET Core application. So, it starts with "dotnet FiddlerOrchestra.Client.NetCore.dll". Find the previously unzipped directory

5. According to the print information of starting .NET Core Fiddler Orchestra Client above, enter http://localhost:8800/ in the browser, and the following figure is displayed. (For the detailed settings here, please go back to the article "Fiddler Orchestra User Guide" shared last time)

Check "Allow remote clients to connect", and then click the [Start!] button to enable it successfully. The corresponding Status information above has changed:

6. In order to make the Fiddler Orchestra Client successfully connect to the Orchestra Controller. According to the introduction user guide above, the Orchestra Controller in Fiddler must first be started.

7. Go back to the .NET Core Fiddler Orchestra Client page. In "Orchestra Connection", enter the IP address of the Orchestra Controller machine (because Xiaoyi installed the Controller and client together, so fill in the loopback address of 127.0.0.1 here), connect Port (3636 by default), and Private key. Then click the button [Connect!], success (the green "Success" is so beautiful!)

On my local machine, I found an error Error The WebSocket protocol is not supported on this platform when connecting. In the end, Xiaoyi chose to install the .NET Core Fiddler Orchestra Client on a remote server host. Wrong guess, the local machine of Xiaoyi is Win7 system, and the remote system is Windows Server 2012. According to online information, if you want to support WebSocket, it seems that you must configure and enable services such as IIS. The little chief has purchased a remote cloud host, which saves you trouble. If you are interested, you can help the little chief to confirm it.

8. Finally, we can connect the proxy of the browser or mobile phone to the port 8866 of the remote server, which is the same as the proxy setting of Fiddler. Finally, in Fiddler, a magical thing happened (see the capture on the left side of the picture below The Device name of the package and the Device name of the .NET Core Fiddler Orchestra Client on the right).

So far, the little chief has completed the actual combat exercise of Fiddler Orchestra. This is a new function of the new version of Fiddler, and there must be some defects. I hope that after the subsequent optimization of Fiddler, it will become easier to use.