Site URL : http://webtest.canoo.com/webtest/manual/WebTestHome.html

• Be aware of XPath, ANT, Groovy scripting, Regex

Installation :

1. Install JDK 5 or Higher version
2. Download build.zip file of Webtest
3. Unzip build.zip file to a folder to the location which do you wish
4. Add the bin/ directory of your WebTest to your path, by opening up the System Properties (press keys WinKey + Pause), selecting the Advanced tab, and the Environment Variables button, then editing the PATH variable in the user variables.
   For example:
   “D:\Webtest\bin”;%PATH%

Running Webtest:

1. Unzip build.zip file to a folder for example —> D:\Webtest\
2. Open a cmd prompt
   
3. Type cd “D:\Webtest\”
4. Type webtest -f webtest.xml wt.createProject
5. You will be asked to type the project name — Enter for example sampleProject

• Now the project D:\Webtest\ sampleProject\ will be created
• Steps 1 through 5 are to be done only one time

6. Type cd “D:\Webtest\ sampleProject\”
7. Type webtest

That’s it…. You will see the webtest will be running …..

If you want add more Webtest testcases

8. Create and save more testcases in location D:\Webtest\   sampleProject\tests\
9. To run again repeat Setps 6 and 7

Video tutorials:

• Installation & Runing : http://opensource.basehaus.com/webtest/screencasts/creating-a-first-webtest-project.htm

• Data driven Test : http://opensource.basehaus.com/webtest/screencasts/data-driven-webtest.htm

• Webtest PPT : http://mguillem.wordpress.com/2008/08/26/webtest-jug-cologne-slides/

Toughtest method

1. To set up SSL for a new host, first you need to import the cert into the keystore so Java can get at it. If you have openssl, you can also use that, e.g. check this one out:

    echo | openssl s_client -connect sc24.sjc.collab.net:443 | openssl x509 -inform PEM -outform DER -trustout  -out outfile.crt
   (this is for Linux systems)
   IE, click on the cert, then go to Cert Details and "copy cert" to a DER
   encoded file.(for Windows Systems)

2. Then once you have the cert in hand, import it into the keystore in the webtest/cubit/ directory.

    $ keytool -import -storepass together -file /tmp/outfile.crt -keystore trust.keystore -alias cubitstore
     Owner: EMAILADDRESS=hostmaster@collab.net, CN=mgr.cubit.example.com, O="CollabNet, Inc.", L=Brisbane, ST=California, C=US
     Issuer: EMAILADDRESS=hostmaster@collab.net, CN=mgr.cubit.example.com, O="CollabNet, Inc.", L=Brisbane, ST=California, C=US
     Serial number: 0
     Valid from: Mon Oct 29 15:46:22 PDT 2007 until: Tue Oct 28 15:46:22 PDT 2008
     Certificate fingerprints:
     MD5:  F7:B1:A8:C6:C6:CE:A1:88:00:EC:F3:7A:5B:63:79:49
     SHA1: 1F:44:88:BE:32:97:A9:28:6F:C5:8C:D7:A0:9B:18:1A:3D:BD:4E:9E
 Trust this certificate? [no]:  yes
 Certificate was added to keystore

Easiest Method

Just setting useInsecureSSL="true" in the config tag ... That's it

step.context.webClient.throwExceptionOnFailingStatusCode property

The webtest is designed to verify a valid HTTP response 200 OK. In certain cases, we are required to verify the error response.
 For instance, while testing the PBL Access priv/ area for an unauthorized user, we should verify if Authorization Required message is displayed.
In this case, the server returns 401 response code.  

In order to verify this response, we override step.context.webClient.throwExceptionOnFailingStatusCode webtest property. The following code snippet is added in the beginning of that module:

In the end of the module, this property should be reverted back. The following code snippet to
revert this behavior:

<                  <setproxy proxyhost="http://myproxy.com" proxyport="3128"/>