Scripting and loggin issue

[dsantamaria]

Hello

I've been playing with this tool for a week or so and so far works amazing, however i have some technical doubts about the scripting, thanks in advance:

- How could i set the value (option) for a <select> DOM element? according to the API documentation, the setValue command only works for inputs and text fields. is there any other option besides jquery (execAndWait) ?

- When i use the setEventName command i cant find what log displays this name, i've tried the raw page data and raw object data .csv's but cant find that expression on ANY log, where should i be looking at?

- Are there any error-logs that show setValue errors? and for that matter any errors on the script?

Thanks!!!!

[pmeenan]

(07-11-2012 04:54 AM)dsantamaria Wrote:  - How could i set the value (option) for a <select> DOM element? according to the API documentation, the setValue command only works for inputs and text fields. is there any other option besides jquery (execAndWait) ?

There is a selectValue command that only works on IE (I think). You pass it the DOM element to do the selection on and the value to select (the value from code, not the displayed string).

If you use javascript, don't use execAndWait unless you are expecting the selection to kick off the action that you want to measure. Use exec and then follow it up with the form submit or button click.

Quote:- When i use the setEventName command i cant find what log displays this name, i've tried the raw page data and raw object data .csv's but cant find that expression on ANY log, where should i be looking at?

That may only work for IE and you need to set it before you perform the step that is going to be measured. I'm not 100% sure it is still reported but it is there from pre-webpagetest days where it was used to test multi-step transactions and measure/database each step independently.

Quote:- Are there any error-logs that show setValue errors? and for that matter any errors on the script?

Sorry, debugging scripts is not terribly easy right now and there is no logging. If you install the pagetest browser plugin on a windows box you can use it to run through a script locally and watch what is happening. I'll update the installer with the release tomorrow (I haven't been releasing the stand-alone installer because it's not terribly good).

For exec commands you can just use the dev tools for the given browser and try executing the script code directly from the console.