The script field gets passed down to webPageTest and defines the test. If you want to run simple tests, that's fine, such as
So if you wanted to check a series of URLs and have them report up into Jenkins one after the other, you simply make a list of them in your CSV file:
01. ,Yahoo front page,navigate%09http%3A%2F%2Fuk.yahoo.com
02. ,Nicks site,navigate%09http%3A%2F%2Fwww.webwob.com
03. ,BBC front page,navigate%09http%3A%2F%2Fwww.bbc.com
I guess you'll notice the url encoding! This threw me for a while as I was doing a bit of noddy self coding. This is really why I've written this page!
I have found a quick and easy way to get the encoding right, including the newlines that are needed for more complex scripts. So now I use notepad++ and an online encoder. Note the encoder builder does say it's ok to copy the source and use it locally. This is good because it gets around any security issues you may have with passwords etc.
Two sample scripts are shown below before and after decoding. The first one involves logging in and going to a secure page: