I couldn't see if cache control headers are being processed correctly. I set up a test against a web site that had the stylesheet (Used in all pages) cache control header set to a max-age value (So it should not be refetched from the server - for max-age seconds). However test run shows the stylesheet repeatedly being fetched from the server (within the session).
Should this be working
Also I am finding the documentation difficult, I am trying to read through the online help (The only authoritive source of VS2005 Tester documentation ) but it is not an easy read in that format - I would prefer a document as a word document that I could print and read in hard copy (and scrawl notes in the magins) or even better a book.
Web Cache Control Headers - and documentation
rasoul
I'm sorry to say that the web test is not honoring the max-age header; this is a bug. The expires header is correctly processed.
Chris Harry
Hi David,
I am sorry you are having difficulties with the documentation. The online help is not the only authoritive source of VS2005 Tester documentation, but it is the most current. At the end of March we will be publishing an update to the documentation, that will be available on MSDN. Unfortunately, this will only be available online, but it will include many new and useful help topics.
You should also be able to access the documentation locally from Visual Studio, by clicking on the Help menu, and then clicking on Contents. The help for team test is under "Development Tools and Languages", "Visual Studio Team System", "Team Edition for Testers".
I am also a huge fan of printing and saving help topics. For both the online and the local Visual Studio help files, you should be able to print the topics by right-clicking in the topic and then clicking Print. I'm afraid we don't produce the help files as Word documents, but you can select the text of a topic (Ctrl-A) and paste it into Word, if that is an absolute requirement.
Thank you,
Nicole Johanson
Márlon
This will definitely be fixed in the next released. I would hope that a fix could be made available in a service pack, but it would need to be reviewed and approved to be included. It would help if you filed an official bug report with Microsoft support.
Nils Nordenbrink