Why are you verifying the images during volume testing? This should be done during functional testing. To verify a page has displayed I would only check one image or some text or both. By performing functional testing first, you can assume that if such and such image shows up then the page appeared properly.
The above responses are valid concerns. While it may be true that functional testing should be performed prior to performance testing, there is merit to what Zorcon is asking. The merit lies in the answer to the question: "What if under load, my server doesn't send the .gifs, or other components of a page? In this case it seems that he should be concerned with an image check. I would vote for picking one or two key gifs upon which to do the image check. I would certainly not do all 93 - as this would create a rather heavy script footprint. On the other hand, if the server is failing to ship the gifs because of stress, the script will likely fail anyway - with or without the image checks. The image checks are there to help you better pinpoint a potential problem source.
Bottom line is you have to decide what is best here. Having image checks makes scripts less maintainable IMHO. Depending on the nature of the business, images can change on a frequent basis, rendering your image checks as broken.
[This message has been edited by jpensyl (edited 04-13-2002).]
Try to use any of shareware tools for this task. Some tools clean cache and have trigger that is waiting till the end of downloading. May be WebWatch will work for you see http://www.geocities.com/ersasoft
Search Ms. Elfriede Dustin post on this topic.
It doesnt matter whether a cat is black or white so long as it catches mice