Monday, October 21, 2013

VS2013 Performance Test Approach and Strategy

Summary-
1. KPI /metrics to identify performance index.
Refer this http://msdn.microsoft.com/en-us/magazine/cc188783.aspx
The next step is to clearly define your metrics. Examples of metrics include the number of orders processed per minute or the number of milliseconds required to execute a request on an ASP page. Metrics allow you to quantify the results of the changes made between each of your test runs. They provide a comparison to the standard defined for your Web application.

2. Saved your load test results in Database for reports comparison against baseline. Identify baseline date
Say SUT test. One can baseline single user test for given scenario consisting of test cases.
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 ContosoServer1 you would use the following command:
    SQLCMD /S ContosoServer1 -i loadtestresultsrepository.sql

  • http://msdn.microsoft.com/en-us/library/dd997707.aspx
    http://msdn.microsoft.com/en-us/library/vstudio/ms182600.aspx

    3. Identify the acceptable response time per request call
    4. Permissible transaction failure or error count.
    5. Combo load test and load test with data driven.
    Say
    Scenario S1
    S1_01 Login
    S1_02 Perform Step 1
    S1_03 Perform Step 2

    Scearnio  S2
    S1_01 Add Details
    S1_02 Perform Step 1
    S1_03 Perform Step 2

    Sceanrio S3
    S1_01 Update Details
    S1_02 Perform Step 1
    S1_03 Perform Step 2

    Broadly I identify 3 high level test scenario. Login, Add and Update

    Ideal Test Condition: Load test With 5 users
    User 1: S1
    User 2: S1
    User 3: S1
    User 4: S1
    User 5: S1
    Same Scenario Different data points different User.
    Run: Concurrent
    Duration of load run: say 30 mins
    Capture Response time


    Real Time Condition: Combo load test with 5 users
    User 1: S1
    User 2: S2
    User 3: S3
    User 4: S2
    User 5: S3
    Different Scenario Different data points different User.
    Run: Concurrent
    Duration of load run: say 30 mins
    Capture Response time




     
    Post a Comment