| || |
Analysis Tool Weirdness
It seems the Analysis tool has a huge dependency on the folder name 'Results' in properly displaying the contents of a test run.
Wasn't sure if anyone else has ran into this before when using the Analysis tool but I've experienced some definitely odd behavior.
I have a local folder on my machine where I extract the contents of the Results.zip file out of Performance Center. I launch Analysis, File -> Open; browse to my newly extracted folder and see no recognizable files to open. Hmm. I browse to the folder using Windows Explorer, double click the .lra and it opens in Analysis. The problem here is, I see no charts, no graphs, no summary report. (This is a custom folder created by me having the name of something like "Run2."
I extract the contents of RawResults.zip to a local folder on my workstation, launch Analysis, File -> Open; browse to that folder, and Analysis recognizes an LRR file which it opens. I CAN see the default report and the small amount of graphs it creates. (Again, a custom folder.)
I follow the same steps in Scenario 1, but extract to a "Results" folder. All of the reports, graphs, and charts display as normally expected. This method kind of lends itself to cluttered unrecognizable folder structure with a ton of "Results" folders sitting out there. Not very descriptive.
So in summary, in order to keep my test runs separated, I create my regular "Run2" folder but have to create a "Results" folder under there in order for Analysis to recognize the LRA using the File -> Open method versus having to browse to the file and double clicking to launch (but also rendering the charts, etc. useless.)
Is this not a royal pain the rear end???
Bug? Feature? I'm a moron?
Just curious about how you folks use the Analysis module and launch/store your results.
Re: Analysis Tool Weirdness
I dont have that much experience with loadrunner yet but something similar has happened to me when trying to save results out of the default directory.
I would get a "failed to create log" message as soon as i would launch a script. It would complete its run normally but the results were unsave-able. Apparently, this also happens when you try to run a script that has a reserved keyword as an action or transaction name.
Im not entirely sure about all this though. But saving the results back into the default folder did solve the issue for me.