How to configure Visual studio load test Database manually?

To configure Visual studio load test Database manually perform following steps:
  1. Open a Visual Studio Command prompt. Type the following text: On a 32-bit version of Windows type: cd “c:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE” -or- On a 64-bit version of Windows type: cd “c:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE”
  2. In that folder, type the following text:
    • SQL Express: SQLCMD /S localhost\sqlexpress /i loadtestresultsrepository.sql
    • SQL: You can install the database to any existing SQL server. For example, if you had a SQL server named Server1 you would use the following command: SQLCMD /S Server1 -i loadtestresultsrepository.sql

Caution The parameters are case sensitive. You must type uppercase S and lowercase i. SQLCMD /S pintu-home -i loadtestresultsrepository.sql

You might also need to specify a user name and password so that you can connect to Server. If so, you would use the following command: SQLCMD /S Server1 -U -P -i loadtestresultsrepository.sql Caution: The parameters are case sensitive.

configure Visual studio load test Database manually

  1. On the Load Test toolbar, choose Manage Test Controllers. The Manage Test Controllers dialog box is displayed.
  2. In the Load Test Results Connection String, click the browse button (…) to display the Connection Properties dialog box. Note:If you change the connection string for a controller, then you must select the controller.
  3. In Server Name, type localhost\sqlexpress or the name of the server that you used in step 2 such as Server1.
  4. Under Log on to the server, choose Use Windows Authentication.
  5. Under Connect to a database, choose Select or enter a database name. Select LoadTest from the drop-down list box.
  6. Choose OK.
  7. Choose Close in the Administer Test Controller dialog box

 

What’s new in JMeter 2.10

jmeter-210_httpsrecorder

JMeter 2.10 has been released. There are few notable changes/improvements in the new JMeter 2.10. Some of the changes are listed below:

 

New CSS/JQuery Tester in View Tree Results

A new CSS/JQuery tester has been added in view tree result. This will help test expressions very easily.

jmeter 2.10 css jquery tester

Improvement in HTTP(S) recorder

“HTTP proxy server” element and has been renamed to “HTTP(S) test script recorder”.

HTTP(S) recording have been improved with many bug fixes around this feature.

jmeter 2.10 httpsrecorder

MongoDB support

Now you can load test MongoDB  using new MongoDB Source Config.

jmeter 2.10 mongodb

Kerberos Authentication support

Authorization Manager now support Kerberos authentication along with Basic_DIGEST

jmeter 2.10 kerberos

New Functions

New functions (__urlencode and __urldecode) are now available to encode/decode URL encoded chars.

jmeter 2.10 newfunctions

Improvement in Distributed testing

  • Number of threads on each node is now reported to controller.
  • Performance improvement on BatchSampleSender
  • Addition of 2 SampleSender modes (StrippedAsynch and StrippedDiskStore)

jmeter 2.10 distributedtesting_threadsumarizer.

Miscellaneous

  • Webservice (SOAP) Request has been removed by default from GUI as Element is deprecated. (Use HTTP Request with Body Data , see also the Template Building a SOAP Webservice Test Plan ), if you need to show it, see property not_in_menu in jmeter.properties
  • HTTP(S) Test Script Recorder if Grouping is set to Put each group in a new Transaction Controller , the Recorder will create Transaction Controller instances with Include duration of timer and pre-post processors in generated sample set to false. This default value reflect more accurately response time.
  • Transaction Controller now sets Response Code of Generated Parent Sampler (if Generated Parent Sampler is checked) to response code of first failing child in case of failure of one of the children, in previous versions Response Code was empty.

For more detail feature click here.