Automated Web Test

The Vugen uses *.dat files to store data used for parameterizing for user-supplied values in a script. But when there are multiple data tables, vugen gets confused as to which data set we are referring to when we run the script.

For example:

In our script if we have two different data tables of login ids names UserId.dat and UID.dat. When we refer to the data column in the table by the column number the data file that is used may not be the one you are intending to use. It is always a better idea to refer to the column by the column name.

Performance Testing Information Resource Site: patterns & practices: Performance Testing Guidance

With a load of “How To”s on a lot of Performance Testing related information this site is a good referenceware. Some of the notable how-tos in this wiki are

• How To: Load Test Web Applications
• How To: Stress Test Web Applications
• How To: Model the Workload for Web Applications
• How To: Conduct Performance Testing with Automated Load Testing Tools

If you are wondering why the apache server you are testing does not run, here is a tool that will make things quite clear. Conflicting ports could be a very common issue is such a case. CurrPorts is a tiny utility that can display all the ports that are open and which programs are using them. You might even be surprised.

Link:http://www.nirsoft.net/utils/cports.html