Hi Rosen,

I used to use FiddlerScript a lot during my days as a manual QA. I tested android and iOS apps. Mobile apps don't have the luxury of the browser's Developer tools, so I used fiddler a lot.

The use cases for FiddlerScript specifically were:

1. I needed to test my app in several different geo locations

For this I had to clean geo data from the requests, which could be present in several places depending on the mobile app settings, and insert new geo data.

I had a script to do that, and also I have made a dropdown menu in the ui, where specific locations were hardcoded, and also an option for a new location
It was really UI friendly to have just a list of needed cities in the menu, instead of a rules set

2 Another case is metrics testing
This time the script took the requests, parsed the request data, and logged only the sent metric events in the console. That was really handy while testing the metrics, because I saw only the list of specific events from several requests payload, and could verify it against the expected result easily

That also had a button in the ui

3 Easy switching between the test servers. That could be done via rules of course, but I liked to have the buttons in the ui for switching with names like Dev Server, Staging Server, etc. They had the rewrite host rule in the FiddlerScript

4 CLI interface
For another task I had an external testing script, that send a lot of requests and compared the results with the expected ones
I needed to identify and research the small subset of responses that contained the faulty data among a large set of correct responses.
I used a simple, yet powerful technique to visualize the results via Fiddler. First, I used Fiddler as a proxy for the script. Second, whenever a response was considered wrong, my script executed a command line, which caused Fiddler to colorize the session in question. This way I was able to look only at responses with problems in the Fiddler UI, since I had them colored for me, and that simplified my task a lot, since I had a lot of responses to check

5 Last but not least, I could share my FiddlerScript with other testers, so they had what they needed in the Fiddler UI. It was easier to share knowledge and tools this way

I can't share the script itself since it is NDA, but that's the idea. For me the FiddlerScript and customizable UI was the killer feature that made Fiddler standout among other similar tools. Hope that this will be added in Fiddler Everywhere, this product seems nice and would be a better alternative to running Fiddler Classic in virtual box, if it had the scripting feature.

Scripting was very useful, but another important thing is that it was a lot of fun also. My interest in this feature essentially started my coding career, and I have been working as a QA Automation Engineer for several years already.

Hope this helps with the evaluation :) Thanks for the great tools!

Hi, 

just wondering if there is any update on adding fiddlerscript to Fiddler Everywhere. That is a killer feature of classic Fiddle, would love to have it on my Mac.

Hi Nick!

Long time no see! And thank you so much for your reply!

I was wondering if there are any plans to introduce command-line features in the future. Specifically, I am interested in knowing whether it would be possible for users to store traffic using command-line.

Kind regards,

Tianming