First, you have noticed the one and only difference that choosing "functional testing" makes.
Second, that sounds like an interesting idea - to make a visualizer that compares the functional differences between two test runs? I think your proposed use of such a tool is an excellent idea. -Mike On 20 Aug 2002 at 15:21, Sosnowski, Andrew P [IT] wrote: > Hi Mike, > > Can you give me an idea of what is the intent behind the Functional Mode > testing checkbox on the front page? > > > This was my plan for a quick and dirty functional test: > We have a Staging environment and a production environment for our app. > When we make a new release of our app I would like to capture and compare > the html responses of running a test script with the new version of the app > on the Staging Environment and the old version still in Production. > Then I would compare the 2 versions of html and make sure that nothing > changed that was not expected to change. > Of course I have to ignore Referrer Headers values and time-stamps and > various cookies that are different on the different servers. > > When I tried using this mode I did find the html within <binary> tags in the > log file. > It looks like it might work as a quick and dirty way to compare. > > Perhaps it might be worth building in some additional support for this kind > of testing into jMeter? For example store html cleaned of timestamps in a > file separate from the log file (or jtl file) > I might be willing to do this if others would find it useful. Also any ideas > of how to make it more useful and general are appreciated > > What do you think? > > Andy > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
