.NET Application Performance & Testing

• .NET testing using Team System
• .NET testing using Selenium
• Automated Testing Tool Development
• Automated testing using HP's QTP & QC

• Involves automating the manual testing process currently in use
  • Developing detailed test cases
  • Standalone test environment
  • Test case scripting
  • Test execution
• Automation of regression testing is most useful

Our automation involves developing

• Test Framework
• Test Suites

Test framework is a test engine, which can be used across projects. It will perform all the required initializations, such as:

• Configuring the required browser, test machine etc.
• Initialize the database
• Initialize the “Test Suite” with some startup configuration
• Execute the “Test Suite”
• Log test results in user friendly format
• Send emails to all stakeholders

A “Test Suite” consists of a set of test cases. Each test case:

• Will test for positive and negative functionality
• Verify with expected results
• Log the test result

• Visual Studio Team Suite
• Selenium and QTP for automating web based application
• Test Complete for automating windows based application

Selenium / QTP / Test Complete is used to record the test scenarios which form the test suite
Visual Studio Team Suite is used:

• To manage the entire test process
  • Can design test scripts using test complete and store it as a test suite
  • Can execute these test suites
  • Will log test results
  • Can program to send automated mails to developers informing of the defect
  • Can log defects in the integrated bug tracker which can be accessed by the entire team
  • Can generate defect metrics and reports

Features of Selenium

• Easy to record and playback
• Intelligent field selection will use IDs, names, or XPath as needed
• Auto complete for all common Selenium commands
• Walk through tests
• Debug and set breakpoints
• Save tests as HTML, Ruby scripts, or any other format
• Support for Selenium user-extensions.js file
• Option to automatically assert the title of every page

We perform “Non functional tests” like

• Performance testing and tuning of the application
• Load testing and arriving at the “Peak load” and “Optimal load” for the application
• Usability Testing
• Compatibility and Interoperability Testing

Performance testing is the process of identifying how an application responds to a specified set of conditions and input. By examining the application's behavior under simulated load conditions, we identify whether the application is trending toward or away from its defined performance objectives.

The main goal of performance testing is to identify how well your application performs in relation to your performance objectives. Some of the other goals of performance testing include the following

• Identify bottlenecks and their causes
• Optimize and tune the platform configuration (both hardware and software) for maximum performance
• Verify the reliability of your application under stress

• Understand the need for performance tuning and establish the performance objective for the application being tested clearly
• Identify the performance counters required to tune the selected parameters (performance goals)
• Identify the scenarios and create scripts to generate the required load
• Setup an environment, which is representative of the live environment
• Execute the tests and monitor the various performance counters
• Analyze the test result and identify if the behavior is tending towards or away from the performance objective
• Identify bottleneck areas and present the results to the team

• Open STA for recording the scripts / test scenarios
• Visual studio team suite for creating the load
• IIS logs and profilers to measure the parameters

Performance tuning of Tanishq application, Printo, Profile for AFS

Load tests are generally performed to verify the application behavior under normal and peak load conditions. We incrementally increase the load from normal to peak load to see how the application performs with varying load conditions. Then we continue to increase the load until we cross the threshold limit for the performance objectives set for the application.

• Identify the key scenarios that are critical for the performance of the application
• Identify the various load conditions at which we will test the application
• Identify the key metrics / counters that are indicative of our defined performance objectives
• Design the test scripts and execute the scripts for the designed load conditions
• Analyze the data, fine tune the parameters and identify the optimal load at which the application works best
• Also identify the thresholds and peak loads and publish them

• Trace files generated by visual studio for wcf calls
• Visual studio team suite for creating the load
• IIS logs and profilers to measure the parameters

Load Testing using Visual Studio Team Suite
Problem Definition

• Product (Handheld device) was re-architected to use WCF instead of web services
• Wanted to study functioning of WCF services under various load conditions
• Performance Goal – Should be able to handle atleast 50 concurrent users within 6 secs

• Enabled the trace files / message files for all WCF calls
• Executed the commonly used scenarios using the client, trace files will log the WCF calls used
• Using this trace file as an input to Visual studio Team system (with WCF load test addon), we create code / test cases
• Also used Visual studio Team systems to configure the profile required for our load test
• Analyzed the test result and identified the bottlenecks

Projects Executed
Tuning for WMS handheld, OMS and Deals for AFS