Convert tests to use SSL connections
You can convert a test that was recorded without SSL connections to use SSL connections.
If you develop performance tests on a lab computer that does not use secure connections, and then you must run the tests against a production server that requires SSL connections, you can add SSL to the server access configurations and reuse the tests.
To convert a server access configuration to use SSL for all associated connections:
- In the Test Navigator, browse to the test, and double-click it.
- Expand the Test Resources section at the top of the test.
- Right-click the server access configuration that corresponds to the server where to add SSL, and then click Add > SSL. An SSL element is added as a child of the server access configuration.
- In the Test Element Details area for the server access configuration, type a new number in Port if the server uses a different port for SSL communication. If the port number is correlated with a server connection variable, select the port number, right-click, and select Go To > Variable: variable_name to navigate to the variable. Change the port number in the server connection variable.
- In the Test Element Details area for the SSL element, make a selection in Protocol, and type or select a name in Cipher.
- Repeat the same steps for all server access configurations to convert to use SSL.
Results
When you run the test, the connections that are associated with the server access configurations use SSL.
Related:
Redirection support for HTTP tests
HTTP test editor overview
Cut and paste in tests
Test variables
Specify the number of allowable URL redirects during test runs
Define performance requirements in tests
Add an authentication folder
Verify expected behavior
Specify error-handling behavior
How loops affect the state of virtual users
Split a test
Split a test page
Merge test pages
Disable and enable secondary HTTP requests
Reuse tests on different hosts: Server connection variables
View a test in the Protocol Data view
Test Siebel applications
Error 404 - Not Found Error 404 - Not Found
The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.