Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you're referring to testing your web application via it's user interface (i.e. automating the clicking of buttons and entering text etc.) rather than unit testing of code-behind classes etc. then I think your best bet is to use either:</p> <p><a href="http://watin.sourceforge.net/" rel="nofollow noreferrer">WatiN</a> (probably the most popular 3rd-party tool for this)<br> or <a href="http://seleniumhq.org/" rel="nofollow noreferrer">Selenium</a>. </p> <p>Both are open source and freely available, and both include the ability to run tests from a command line thus enabling integration into your test harness and continuous integration cycle.</p> <p><strong>EDIT:</strong></p> <p>In response to Michael's comment on this answer:</p> <p>No, as far as I know, neither WatiN nor Selenium will run your previously created <em>MS WebTest</em> web tests.</p> <p>Also, I did some further research and discovered that you also cannot run those <em>MS WebTest</em> web tests without having Visual Studio Team System/Testing Edition installed. </p> <p>Your Visual Studio 2008 Professional has <em>unit</em> testing built-in, and this can be automated at the command line using the <a href="http://msdn.microsoft.com/en-us/library/ms182489%28VS.90%29.aspx" rel="nofollow noreferrer"><code>MSTEST.EXE</code></a> command-line tool. </p> <p>Incidentally, this exact same tool is also used to automate the running of <em>web</em> tests from the command line in Visual Studio Team System, as detailed <a href="http://msdn.microsoft.com/en-US/library/ms243149%28v=VS.80%29.aspx" rel="nofollow noreferrer">here</a>.</p> <p>Unfortunately, the <code>MSTEST.EXE</code> tool is only 18kb in size, and relies upon loading numerous external assemblies in order to delegate the actual testing functionality to the relevant type of test. In the case of web tests, your Professional edition of Visual Studio will not have those assemblies installed, and attempting to run a web test will result in the following error message:</p> <blockquote> <p><code>File extension specified '.webtest' is not a valid test extension.</code></p> </blockquote> <p>There is <a href="https://stackoverflow.com/questions/291350/what-is-needed-to-execute-visual-studio-2005-web-tests">another StackOverflow question regarding this same problem</a> (it's based on VS 2005, although the same applies to 2008).</p> <p>It seems that <code>MSTEST.EXE</code>, despite being a command line tool, is fairly tightly "coupled" with a Visual Studio installation, and is difficult to separate, for example when users wish to deploy the <code>MSTEST</code> functionality to a build server for continuous integration without having a "full" installation of Visual Studio on the same machine. It seems this is very difficult to actually achieve, although a few people have posted <a href="http://www.delarou.net/weblog/PermaLink,guid,05d6228c-365d-4279-b66c-cc027dfdba89.aspx" rel="nofollow noreferrer">blog entries</a> and <a href="http://www.shunra.com/shunrablog/index.php/2009/04/23/running-mstest-without-visual-studio/" rel="nofollow noreferrer">articles</a> regarding attempts (albeit somewhat "hacky") to achieve this.</p> <p>That said, however, it's still not possible to run MS WebTest <em>web tests</em> without Visual Studio Team System/Testing Edition.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload