How to upgrade NTLM testcases from Load Tester 4.1 to 4.2
Due to the scope of changes in the 4.2 release and the improvements to our NTLM support, testcases using NTLM that were created in Load Tester 4.1 and earlier versions are not automatically upgraded with the required 4.2 configuration settings. The result is testcases that will not be able to perform the NTLM authentication – therefore causing a failure of every transaction that requires authentication. Fortunately, the manual upgrade process is relatively easy:
Step 1: Select the testcase and run the Testcase Configuration wizard. You can do this from the pop-up menu in the Navigator view (Configure > Configure for Replay) or from the magic wand toolbar button from the testcase editor. When the wizard appears, choose the Configure user identity for connection authentication option and press Next. If your testcase used only a single NTLM identity, then choose the Share the same username… option and press Next to enter the credentials. Otherwise, choose the Use an existing dataset… option and press Next to configure the fields.
Step 2: Edit the testcase properties: Select the testcase in the Navigator view and select Properties from the pop-up menu. On the General tab, you will find a Maximum number of connections per host setting. Previous versions of Load Tester will have set this value to 1 for NTLM testcases. Set this to 2 for IE 7 and earlier behavior. IE 8 and later use 6 connections per host.
You will need to repeat this for each NTLM testcase that was built in 4.1 or earlier versions that you want to run in 4.2. We apologize for the inconvenience of this upgrade, but we think the NTLM improvements we’ve made are well worth the effort!
Chris Merrill, Chief Engineer
When his dad brought home a Commodore PET computer, Chris was drawn into computers. 7 years later, after finishing his degree in Computer and Electrical Engineering at Purdue University, he found himself writing software for industrial control systems. His first foray into testing software resulted in an innovative control system for testing lubricants in automotive engines. The Internet grabbed his attention and he became one of the first Sun Certified Java Developers. His focus then locked on performance testing of websites. As Chief Engineer for Web Performance since 2001, Chris now spends his time turning real-world testing challenges into new features for the Load Tester product.