server

Jul 28 2009   10:00AM GMT

Five Technical Details to understand before performing Load Testing on a software product

Posted by: Jaideep
technical, load testing, testing, software product, framework, Software application, .Net, J2EE, server, server application, presentation server, application server, database server, MS SQL Server, Oracle, Apache, Websphere, IIS, OS, operating system, hardware configuration, RAM, processor, harddisk, LAN, dial-up

1. Framework: What is the framework being used in the application? For example it may be .Net or J2EE or any other.

2. Servers: What all server services you are using to run/ use this application? What standard server applications are used for Presentation, Application and Database level? Some examples could be MS SQL Server, Oracle, Apache, Websphere, IIS etc.

3. Number of machines: Are these servers running on same machine or different machines. If different machines how many machines and what servers specfically on which machine.

4. Details of these machines: The details of the machines running all these server applications or server services. Details would include Operating System, Hardware configuation – like Hard disks, RAM, processors etc.

5. Access details: Last but not the least important point is how the users will be accessing the application – via LAN, through dial-up, through internet, through some specific port and third party tool etc.

Jul 24 2009   10:00AM GMT

Four Environment Essentials to know before performing load testing

Posted by: Jaideep
load testing, testing, quality, software product, server, Test Server, production server, Staging Server, server configuration, n-tier, 2-tier, 3-tier, Software application, n-tier application, application, browser, browser version, architecture, performance, protocol

Which Server: Where is the load testing intended to be performed? Is it the test server, production server or staging server where load testing is to be performed? If it is being performed on Production Server, it is ok. Otherwise if it is to be performed on test or staging server, be careful that it is as near to production server in terms of configuration and setup as possible. It may give wrong projections if there is a wide gap in environment which is to be used in real versus the environment on which the test is performed.

How many Tiers: It is very important to understand how many tier application is, on which the load testing is to be performed. The n-tier count should include the client also.

What Browsers: Be very clear and specific on defining what all browsers are meant to be used for running this application (if this is a web application). The browser and its version is very important to conduct the load testing as each browser behavior, architecture and performance varies. Even between the different versions of the same browser.

What Protocols: Whether this is a client server application, web based application or n-tier application – identifying what protocols you are using to run the application is very important.