Current time: 12-11-2017, 10:23 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Need desktop version of PageTest
06-28-2013, 12:48 AM
Post: #11
RE: Need desktop version of PageTest
You can get a reasonably recent version of the msi installer here: https://code.google.com/p/webpagetest/downloads/list
Visit this user's website Find all posts by this user
Quote this message in a reply
07-20-2013, 12:12 AM
Post: #12
RE: Need desktop version of PageTest
(06-28-2013 12:48 AM)pmeenan Wrote:  You can get a reasonably recent version of the msi installer here: https://code.google.com/p/webpagetest/downloads/list

Greetings

Okay, looks like I'll have to admit to a fading memory... again. re: The Desktop version of PageTest:

I've been digging around but haven't been able to find it. What is the default location where the data and error logs are posted, and can it be changed? Even when logging is turned on, I can't seem to find where the files are being generated.

Also, although I know it's called PageTest not SiteTest, while it's navigating the script there are waterfalls being shown for each page as it progresses. Was there a command that allowed one to snapshot those, and their associated data, during the script run? The earlier version used to hold the waterfall and such so that you could save the different items from the 'Files' dropdown (albeit only the first completed page). The current one seems to flush it all a couple of seconds after the page completes. 'Ya gotta be pretty fast to catch it that way. :-) I couldn't remember if there was something like a postData <switch> option that would (could) let the script trigger a save/export all data at each stage. Or am I just fondly remembering one of those wish-list items?

Thanx

Robert
Find all posts by this user
Quote this message in a reply
07-20-2013, 02:54 AM
Post: #13
RE: Need desktop version of PageTest
The desktop UI doesn't log the performance data out. Those are only saved when it is automated. If you're tracking down issues the best way is to use debugview which will display the internal error messages for debugging (a debug build will generate a whole ton of them - not sure how much you'll get from a release build).
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)