Fiddler .saz recording import facility (as alternative to HAR files)

[davidcampbelldc]

Suggestion : Fiddler from Telerik can create a .saz recording, very similar to a .har.
That integration would be a huge + for me as a competitive feature.
I like the Fiddler layout because each request/response is clearer IMHO

[davidcampbell-dc]

Note: .saz files are ZIP archives containing individual request/response pairs as raw text files. The conversion path would be: parse .saz → normalise to the same internal format we use for HAR → feed into existing test plan generation pipeline. Should be a relatively clean addition since the heavy lifting (correlation, test plan generation) already exists for HAR.

[davidcampbelldc]

Priority bumped: 4. LOW → 2. HIGH

This now also addresses #91 (HAR recording gaps). Chrome DevTools HAR exports silently drop response bodies for large pages (e.g. Salesforce Lightning bootstrap), breaking correlation. Fiddler proxy-level capture gets complete data.

Approach: .saz → HAR conversion endpoint on har-service, then existing pipeline handles everything unchanged.

[davidcampbelldc]

Meeting Notes — Testing Mavens Partnership Meeting (Feb 16, 2026)

Related context: Testing Mavens uses multiple recording methods depending on the client:

• HAR files (~80% of scripts) — used for internal corporate testing
• JMeter HTTP Recorder (proxy) — used when enterprise proxy limitations prevent other methods
• Manual scripting — used in restrictive enterprise environments

A new issue #94 has been created specifically for JMeter HTTP Recorder support. Together with this Fiddler .saz issue, these represent the full set of alternative input formats needed for the Testing Mavens partnership.

David confirmed that LoadMagic converts all inputs to HAR internally, so all alternative format support follows the same architectural pattern.

[davidcampbelldc]

Completed: Fiddler .saz import implemented server-side (SAZ→HAR conversion in har-service). Deployed to dev. Regression tests added.