Prequisites - 1. Visual Studio Team System - VSTS (preferably 2005) 2. Selenium .NET Client Driver {http://archiva.openqa.org/repository/releases/org/openqa/selenium /selenium-remote-control/1.0-beta-1/selenium-remote-control-1.0-beta-1-dist.zip} On unzipping the package one folder dotnet will be found.) 3. NUnit (2.4.7){http://www.nunit.org/download.html > download NUnit-2.4.7-net-1.1.msi} Steps - 1. Launch VSTS > File > New > Project. 2. Select Visual C# > Test > Test Project > Click Ok 3. This will open AuthorisingTest.txt and UnitTest1.cs files. 4. Click on UnitTest1.cs file and replace the existing code with following - **************************************************************** This is a simple test over google where Search is performed over "Selenium OpenQA" string and search results are verified. **************************************************************** 5. On the RHS under Solution Explorer right click on References > Add References > Browser to the dotnet directory which was 2nd prerequisite. Select following dll files - nmock.dll, nunit.core.dll, nunit.framework.dll, ThoughtWorks.Selenium.Core.dll, ThoughtWorks.Selenium.IntegrationTests.dll, ThoughtWorks.Selenium.UnitTests.dll and click on Ok button 6. Under Build menu click on Build Solution > If compilation goes fine then you should see this message - *************************************************** Compile complete -- 0 errors, 0 warnings TestProject1 -> D:\Test\TestProject1\TestProject1\bin\Debug\TestProject1.dll ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ========== *************************************************** Hence this will create a dll - TestProject1.dll where TestProject1 is the name of the project given during step 1 7. Launch NUnit as Start > Programs > NUnit 2.4.7 > Click on File > Open Project. 8. Browser to the TestProject1.dll which was created in step 6 and click on Open button. 9. Before running the Tests we need start selenium server. Launch command prompt and browse to the director where selenium-server folder is installed. For me it is under C drive - ************************************************* C:\Program Files\Selenium and other files\selenium-remote-control-0.9.0\server>j ava -Dhttp.proxyHost=192.168.1.14 -Dhttp.proxyPort=80 -jar selenium-server.jar - proxyinjectionmode ************************************************* This should get the selenium server running with following info - ************************************************* The selenium server will execute in proxyInjection mode. Jul 22, 2008 4:43:26 PM org.mortbay.http.HttpServer doStart INFO: Version Jetty/0.9.0 Jul 22, 2008 4:43:26 PM org.mortbay.util.Container start INFO: Started HttpContext[/,/] Jul 22, 2008 4:43:26 PM org.mortbay.util.Container start INFO: Started HttpContext[/selenium-server,/selenium-server] Jul 22, 2008 4:43:26 PM org.mortbay.util.Container start INFO: Started HttpContext[/selenium-server/driver,/selenium-server/driver] Jul 22, 2008 4:43:26 PM org.mortbay.http.SocketListener start INFO: Started SocketListener on 0.0.0.0:4444 Jul 22, 2008 4:43:26 PM org.mortbay.util.Container start INFO: Started org.mortbay.jetty.Server@a62fc3 ************************************************* Notice: I had to explicitly declare our n/w proxy as google is out side Iteamic n/w and to be able to access we should go through n/w proxy. 10. Now click on Run button on NUnit window and enjoy the tests being launched in IE :-) To Summerize - Build the Project in VSTS. Run Selenium Server. Take the dll file generated after building the project file and click on Run button. In absense of VSTS same can be achieved Visual Studio 2005 as well. Follow these steps instead of one described in Description below. - 1. Launch MS Visual Studio 2005 > File > New > Project 2. Select Visual C# > Class Library > Name your project > Click OK 3. A Class (.cs) is already created. Rename it as appropriate This should get you going.
Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred