Automated OpenSTA Scripting tool
I have been using and teaching OpenSTA for the last 5 years, and have grown to like it very much. It is however very labor intensive to model scripts. I have created a tool I call "OpenSTA Script Buddy" which automates the editing of scripts. It can optionally;
- modify code to get around known bugs
- add code which automates debugging and validation tasks,
- intelligently filter URLS (and associated load response and disconnect commands) by domain and/or by keyword searches (e.g. it can identify and remove requests to external ad sites, analytics engines, livesales sites, etc).
- reformat post bodies to make long XML and/or URL encoded strings easy to read and model
- disable caching in the script
- disable keep-alive timers globally (can cause no data available in some cases when doing LOAD RESPONSE_INFO)
It does not do any sort of automatic correlation AT THIS TIME, but if I sell enough of the this version, I might invest the time and money to attempt automatic correlation.
If your organization does a LOT of OpenSTA scripting and is willing to invest in a tool that can cut scripting time from a day or so to a matter of hours, please contact me offline. I am interested in hearing from you. I need feedback on functionality and beta testers. This tool will not be free, so if you are a student who is "just learning OpenSTA" or work for a company that solves problems by brute force cheap labor, please don't contact me. Unless I hear a compelling reason to do so, this trial will be limited to companies based in the US or Europe (this is where 100% of my business comes from, and I won't chase business outside this area no matter how "great the future prospects are if I could only do it for free this time".)
Re: Automated OpenSTA Scripting tool
A number of folks have asked for more information on what Script Buddy (TM) can do. I've started to write some doc but the tool is evolving based on beta test users input, so the doc is a bit of a moving target.
Here are my notes (typos and all!) that will eventually hammered into proper documentation.