The open-source LPT tool JMeter provides an excelent framework for load- and performance-testing several server types. Downloadable from http://jmeter.apache.org/.
With its full multithreading framework JMeter allows concurrent sampling by many threads and simultaneous sampling of different functions by seperate thread groups.
A GUI allows fast operation and high usability. Test szenarios can be recorded via a proxy server be by replayed offline. It is completely portable and 100 % Java.
An alternative would be the automation tool "Sahi" (http://sahi.co.in/w/sahi). The great advantage is that it's independent from the used browser and operating system.
Install and use Selenium RC , see http://seleniumhq.org
Microsoft provides a module called Web Service Software Factory (WSSF) for Visual Studio 2008. According to preleases this functionality is included in the release of Studio 2010. This can be downloaded at this link (http://msdn.microsoft.com/en-us/library/bb931187.aspx). All produced code follows Message-patterns and many conventions. Furthermore, data contracts and services are visualized in understandable models which allow easy documentation (they have a UML notation - could be a UML profile in backend). The code (including test cases) is generated automatically. .Net in C# and VB.Net is available for the generation. The solution with all projects it automatically set up and can be easily extended by using own code such as references to other modules. The usage of it can be sketched like the following instructions. Please note, that the overall usage needs some training and is not documentable in this CMS system precisely. See the useful walkthrough from CodeProject to fully understand how it could be used in a real project and to identify the benefits: click
Now you can build and use your service. Several endpoints can be used and configured according your connection requirements. Binding variants such HTTPBinding can be used to bind the service to different addresses using different names etc. Not all binding variants are available in this version (only the desired usages). In your service configuration security constraints such as the authentication mechanism can be set like for classical WCF or ASMX services. Futhermore, test cases could be generated. The models can be exported by using screenshots. The service can easily be modified, because of strict separation of own .NET code and the generated code. For optimal results try to use the modeled data contracts only as templates for the internally used data structures. However, it is sometimes useful to start the development by visually experimenting with this data contracts model. (Sry for re-posting, but the solution-problem linking got lost)