blocks|key|2999313|text|我正要开始在我正在做的一个新项目上做JavaScript+TDD。我目前的计划是使用QUnit进行单元测试。在开发时，只需在浏览器中刷新测试页面即可运行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2999314|为了实现持续集成(并确保测试在所有浏览器中运行)，我将使用Selenium在每个浏览器中自动加载测试工具，并读取结果。这些测试将在每次签入到源代码管理时运行。|2999315|我还将使用JSCoverage来获得测试的代码覆盖率分析。这也将通过Selenium实现自动化。|2999316|我现在正在设置中。一旦我敲定了设置，我将用更准确的细节更新这个答案。|2999317|2999318|测试工具：|2999319|2999320|qunit|unordered-list-item|2999321|JSCoverage|2999322|Selenium|2999323|2999324|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Test-driven_development|1|http://docs.jquery.com/QUnit|2|http://selenium.openqa.org/|3|http://siliconforks.com/jscoverage/|4|5|6^0|T|3|0|16|5|1|0|T|8|2|0|5|A|3|0|0|0|0|0|0|5|4|0|0|A|5|0|0|8|6|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]|$A|1G|B|1H|1|1I]]|C|$]]|$1|D|3|E|5|6|7|1J|8|@]|9|@$A|1K|B|1L|1|1M]]|C|$]]|$1|F|3|G|5|6|7|1N|8|@]|9|@$A|1O|B|1P|1|1Q]]|C|$]]|$1|H|3|I|5|6|7|1R|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1S|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1T|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|1U|8|@]|9|@]|C|$]]|$1|N|3|O|5|P|7|1V|8|@]|9|@$A|1W|B|1X|1|1Y]]|C|$]]|$1|Q|3|R|5|P|7|1Z|8|@]|9|@$A|20|B|21|1|22]]|C|$]]|$1|S|3|T|5|P|7|23|8|@]|9|@$A|24|B|25|1|26]]|C|$]]|$1|U|3|-4|5|6|7|27|8|@]|9|@]|C|$]]|$1|V|3|-4|5|6|7|28|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]|13|$5|Y|Z|10|C|$11|14]]|15|$5|Y|Z|10|C|$11|16]]|17|$5|Y|Z|10|C|$11|18]]|19|$5|Y|Z|10|C|$11|14]]|1A|$5|Y|Z|10|C|$11|18]]|1B|$5|Y|Z|10|C|$11|16]]]]

I'm just about to start doing JavaScript <a href="https://en.wikipedia.org/wiki/Test-driven_development" rel="nofollow noreferrer">TDD</a> on a new project I am working on. My current plan is to use <a href="http://docs.jquery.com/QUnit" rel="nofollow noreferrer">QUnit</a> to do the unit testing. While developing the tests can be run by simply refreshing the test page in a browser.
For continuous integration (and ensuring the tests run in all browsers), I will use <a href="http://selenium.openqa.org/" rel="nofollow noreferrer">Selenium</a> to automatically load the test harness in each browser, and read the result. These tests will be run on every checkin to source control.
I am also going to use <a href="http://siliconforks.com/jscoverage/" rel="nofollow noreferrer">JSCoverage</a> to get code coverage analysis of the tests. This will also be automated with Selenium.
I'm currently in the middle of setting this up. I'll update this answer with more exact details once I have the setup hammered out.
<hr />
Testing tools:
<ul>
<li><a href="http://docs.jquery.com/QUnit" rel="nofollow noreferrer">qunit</a></li>
<li><a href="http://siliconforks.com/jscoverage/" rel="nofollow noreferrer">JSCoverage</a></li>
<li><a href="http://selenium.openqa.org/" rel="nofollow noreferrer">Selenium</a></li>
</ul>

blocks|key|2999442|text|我是js-test-driver的铁杆粉丝。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2999443|它在CI环境中工作良好，能够捕获实际的浏览器进行跨浏览器测试。|2999444|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/js-test-driver/|1|https://en.wikipedia.org/wiki/Continuous_integration^0|2|E|0|0|2|2|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

I'm a big fan of <a href="http://code.google.com/p/js-test-driver/" rel="nofollow noreferrer">js-test-driver</a>.
It works well in a <a href="https://en.wikipedia.org/wiki/Continuous_integration" rel="nofollow noreferrer">CI</a> environment and is able to capture actual browsers for cross-browser testing.

blocks|key|755958|text|我最近读了Bruno的一篇文章，他使用JSUnit并在此基础上创建了一个JsMock框架……非常有趣。我正在考虑使用他的工作来开始对我的JavaScript代码进行单元测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|755959|Mock+JavaScript+or+How+to+unit+test+JavaScript+outside+the+Browser+environment|offset|length|755960|entityMap|0|LINK|mutability|MUTABLE|url|http://brunofigueiredo.com/post/Mock-Javascript-or-How-to-unit-test-Javascript-outside-the-Browser-environment-Part-1.aspx^0|0|0|26|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I recently read an article by Bruno using JSUnit and creating a JsMock framework on top of that... very interesting. I'm thinking of using his work to start unit testing my JavaScript code.
<a href="http://brunofigueiredo.com/post/Mock-Javascript-or-How-to-unit-test-Javascript-outside-the-Browser-environment-Part-1.aspx" rel="nofollow noreferrer">Mock JavaScript or How to unit test JavaScript outside the Browser environment</a>

blocks|key|5254241|text|我只是got+Hudson+CI+to+run+JasmineBDD+(无头)，至少对于纯JavaScript单元测试是这样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5254242|(Hudson通过shell运行Java，运行Envjs，运行JasmineBDD。)|5254243|不过，我还没有得到一个像prototype这样的大型库。|5254244|entityMap|0|LINK|mutability|MUTABLE|url|http://skaug.no/ingvald/2010/10/javascript-unit-testing.html^0|3|V|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

I just <a href="http://skaug.no/ingvald/2010/10/javascript-unit-testing.html" rel="nofollow noreferrer">got Hudson CI to run JasmineBDD</a> (headless), at least for pure JavaScript unit testing.
(Hudson running Java via shell, running Envjs, running JasmineBDD.)
I haven't got it to play nice with a big library yet, though, like prototype.

blocks|key|5253880|text|调查YUITest|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5253881|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.yahoo.com/yui/yuitest/^0|2|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Look into <a href="http://developer.yahoo.com/yui/yuitest/" rel="nofollow noreferrer">YUITest</a>

blocks|key|2999505|text|我同意JSUnit在某种程度上是垂死的。我们刚刚用YUI+Test替换了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2999506|与使用qUnit的示例类似，我们使用Selenium运行测试。我们独立于其他Selenium测试运行此测试，原因很简单，因为它没有普通UI回归测试所具有的依赖项(例如，将应用程序部署到服务器)。|offset|length|2999507|首先，我们有一个包含在所有测试JavaScript文件中的基本HTML文件。它负责设置YUI实例、测试运行器、YUI.Test.Suite对象以及Test.Case。它具有可以通过Selenium访问的方法，以运行测试套件，检查测试运行器是否仍在运行(完成后才能获得结果)，并获得测试结果(我们选择了JSON格式)：|2999508|var+yui_instance;+//+The+YUI+instance
var+runner;++//+The+YAHOO.Test.Runner
var+Assert;++++//+An+instance+of+YAHOO.Test.Assert+to+save+coding
var+testSuite;+//+The+YAHOO.Test.Suite+that+will+get+run.

/**
+*+Sets+the+required+value+for+the+name+property+on+the+given+template,+creates
+*+and+returns+a+new+YUI+Test.Case+object.
+*
+*+@param+template+the+template+object+containing+all+of+the+tests
+*/
function+setupTestCase(template)+{
++++template.name+=+"jsTestCase";
++++var+test_case+=+new+yui_instance.Test.Case(template);
++++return+test_case;
}

/**
+*+Sets+up+the+test+suite+with+a+single+test+case+using+the+given
+*+template.
+*
+*+@param+template+the+template+object+containing+all+of+the+tests
+*/
function+setupTestSuite(template)+{
++++var+test_case+=+setupTestCase(template);
++++++testSuite+=+new+yui_instance.Test.Suite("Bond+JS+Test+Suite");
++++++testSuite.add(test_case);
}

/**
+*+Runs+the+YAHOO.Test.Suite
+*/
function+runTestSuite()+{
++++runner+=+yui_instance.Test.Runner;
++++Assert+=+yui_instance.Assert;

++++runner.clear();
++++runner.add(testSuite);
++++runner.run();
}

/**
+*+Used+to+see+if+the+YAHOO.Test.Runner+is+still+running.++The
+*+test+results+are+not+available+until+it+is+done+running.
+*/
function+isRunning()+{
++++return+runner.isRunning();
}

/**
+*+Gets+the+results+from+the+YAHOO.Test.Runner
+*/
function+getTestResults()+{
++++return+runner.getResults(yui_instance.Test.Format.JSON);
}|code-block|syntax|javascript|2999509|至于Selenium方面，我们使用了参数化测试。我们在Internet+Explorer和Firefox中的data方法中运行测试，将测试结果解析为对象数组列表，每个数组包含浏览器名称、测试文件名、测试名称、结果(通过、失败或忽略)和消息。|2999510|实际的测试只是断言测试结果。如果不等于"pass“，则通过YUI测试结果返回的消息使测试失败。|2999511|@Parameters
public+static+List<Object[]>+data()+throws+Exception+{
++++yui_test_codebase+=+"file:///c://myapppath/yui/tests";

++++List<Object[]>+testResults+=+new+ArrayList<Object[]>();

++++pageNames+=+new+ArrayList<String>();
++++pageNames.add("yuiTest1.html");
++++pageNames.add("yuiTest2.html");

++++testResults.addAll(runJSTestsInBrowser(IE_NOPROXY));
++++testResults.addAll(runJSTestsInBrowser(FIREFOX));
++++return+testResults;
}

/**
+*+Creates+a+Selenium+instance+for+the+given+browser,+and+runs+each
+*+YUI+Test+page.
+*
+*+@param+aBrowser
+*+@return
+*/
private+static+List<Object[]>+runJSTestsInBrowser(Browser+aBrowser)+{
++++String+yui_test_codebase+=+"file:///c://myapppath/yui/tests/";
++++String+browser_bot+=+"this.browserbot.getCurrentWindow()"
++++List<Object[]>+testResults+=+new+ArrayList<Object[]>();
++++selenium+=+new+DefaultSelenium(APPLICATION_SERVER,+REMOTE_CONTROL_PORT,+aBrowser.getCommand(),+yui_test_codebase);
++++try+{
++++++++selenium.start();

++++++++/*
+++++++++*+Run+the+test+here
+++++++++*/
++++++++for+(String+page_name+:+pageNames)+{
++++++++++++selenium.open(yui_test_codebase+%2B+page_name);
++++++++++++//Wait+for+the+YAHOO+instance+to+be+available
++++++++++++selenium.waitForCondition(browser_bot+%2B+".yui_instance+!=+undefined",+"10000");
++++++++++++selenium.getEval("dom=runYUITestSuite("+%2B+browser_bot+%2B+")");

++++++++++++//+Output+from+the+tests+is+not+available+until
++++++++++++//+the+YAHOO.Test.Runner+is+done+running+the+suite
++++++++++++selenium.waitForCondition("!"+%2B+browser_bot+%2B+".isRunning()",+"10000");
++++++++++++String+output+=+selenium.getEval("dom=getYUITestResults("+%2B+browser_bot+%2B+")");

++++++++++++JSONObject+results+=+JSONObject.fromObject(output);
++++++++++++JSONObject+test_case+=+results.getJSONObject("jsTestCase");
++++++++++++JSONArray+testCasePropertyNames+=+test_case.names();
++++++++++++Iterator+itr+=+testCasePropertyNames.iterator();

++++++++++++/*
+++++++++++++*+From+the+output,+build+an+array+with+the+following:
+++++++++++++*+++++Test+file
+++++++++++++*+++++Test+name
+++++++++++++*+++++status+(result)
+++++++++++++*+++++message
+++++++++++++*/
++++++++++++while(itr.hasNext())+{
++++++++++++++++String+name+=+(String)itr.next();
++++++++++++++++if(name.startsWith("test"))+{
++++++++++++++++++++JSONObject+testResult+=+test_case.getJSONObject(name);
++++++++++++++++++++String+test_name+=+testResult.getString("name");
++++++++++++++++++++String+test_result+=+testResult.getString("result");
++++++++++++++++++++String+test_message+=+testResult.getString("message");
++++++++++++++++++++Object[]+testResultObject+=+{aBrowser.getCommand(),+page_name,+test_name,+test_result,+test_message};
++++++++++++++++++++testResults.add(testResultObject);
++++++++++++++++}
++++++++++++}
++++++++}
++++}+finally+{
++++++++//+If+an+exception+is+thrown,+this+will+guarantee+that+the+selenium+instance
++++++++//+is+shut+down+properly
++++++++selenium.stop();
++++++++selenium+=+null;
++++}
++++return+testResults;
}

/**
+*+Inspects+each+test+result+and+fails+if+the+testResult+was+not+"pass"
+*/
@Test
public+void+inspectTestResults()+{
++++if(!this.testResult.equalsIgnoreCase("pass"))+{
++++++++fail(String.format(MESSAGE_FORMAT,+this.browser,+this.pageName,+this.testName,+this.message));
++++}
}|2999512|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Selenium_%2528software%2529^0|0|I|8|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|16|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|19|8|@]|9|@]|A|$K|L]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I am in agreement that JSUnit is kind of dying on the vine. We just finished up replacing it with YUI Test.
Similar to the example using qUnit, we are running the tests using <a href="https://en.wikipedia.org/wiki/Selenium_%28software%29" rel="nofollow noreferrer">Selenium</a>. We are running this test independently from our other Selenium tests simply because it does not have the dependencies that the normal UI regression tests have (e.g. deploying the application to a server).
To start out, we have a base JavaScript file that is included in all of our test HTML files. This handles setting up the YUI instance, the test runner, the YUI.Test.Suite object as well as the Test.Case. It has methods that can be accessed via Selenium to run the test suite, check to see if the test runner is still running (results are not available until after it's done), and get the test results (we chose JSON format):
<pre><code>var yui_instance; // The YUI instance
var runner; // The YAHOO.Test.Runner
var Assert; // An instance of YAHOO.Test.Assert to save coding
var testSuite; // The YAHOO.Test.Suite that will get run.

/**
 * Sets the required value for the name property on the given template, creates
 * and returns a new YUI Test.Case object.
 *
 * @param template the template object containing all of the tests
 */
function setupTestCase(template) {
 template.name = &quot;jsTestCase&quot;;
 var test_case = new yui_instance.Test.Case(template);
 return test_case;
}

/**
 * Sets up the test suite with a single test case using the given
 * template.
 *
 * @param template the template object containing all of the tests
 */
function setupTestSuite(template) {
 var test_case = setupTestCase(template);
 testSuite = new yui_instance.Test.Suite(&quot;Bond JS Test Suite&quot;);
 testSuite.add(test_case);
}

/**
 * Runs the YAHOO.Test.Suite
 */
function runTestSuite() {
 runner = yui_instance.Test.Runner;
 Assert = yui_instance.Assert;

 runner.clear();
 runner.add(testSuite);
 runner.run();
}

/**
 * Used to see if the YAHOO.Test.Runner is still running. The
 * test results are not available until it is done running.
 */
function isRunning() {
 return runner.isRunning();
}

/**
 * Gets the results from the YAHOO.Test.Runner
 */
function getTestResults() {
 return runner.getResults(yui_instance.Test.Format.JSON);
}
</code></pre>
As for the Selenium side of things, we used a parameterized test. We run our tests in both Internet Explorer and Firefox in the data method, parsing the test results into a list of Object arrays with each array containing the browser name, the test file name, the test name, the result (pass, fail or ignore) and the message.
The actual test just asserts the test result. If it is not equal to &quot;pass&quot; then it fails the test with the message returned from the YUI Test result.
<pre><code>@Parameters
public static List&lt;Object[]&gt; data() throws Exception {
 yui_test_codebase = &quot;file:///c://myapppath/yui/tests&quot;;

 List&lt;Object[]&gt; testResults = new ArrayList&lt;Object[]&gt;();

 pageNames = new ArrayList&lt;String&gt;();
 pageNames.add(&quot;yuiTest1.html&quot;);
 pageNames.add(&quot;yuiTest2.html&quot;);

 testResults.addAll(runJSTestsInBrowser(IE_NOPROXY));
 testResults.addAll(runJSTestsInBrowser(FIREFOX));
 return testResults;
}

/**
 * Creates a Selenium instance for the given browser, and runs each
 * YUI Test page.
 *
 * @param aBrowser
 * @return
 */
private static List&lt;Object[]&gt; runJSTestsInBrowser(Browser aBrowser) {
 String yui_test_codebase = &quot;file:///c://myapppath/yui/tests/&quot;;
 String browser_bot = &quot;this.browserbot.getCurrentWindow()&quot;
 List&lt;Object[]&gt; testResults = new ArrayList&lt;Object[]&gt;();
 selenium = new DefaultSelenium(APPLICATION_SERVER, REMOTE_CONTROL_PORT, aBrowser.getCommand(), yui_test_codebase);
 try {
 selenium.start();

 /*
 * Run the test here
 */
 for (String page_name : pageNames) {
 selenium.open(yui_test_codebase + page_name);
 //Wait for the YAHOO instance to be available
 selenium.waitForCondition(browser_bot + &quot;.yui_instance != undefined&quot;, &quot;10000&quot;);
 selenium.getEval(&quot;dom=runYUITestSuite(&quot; + browser_bot + &quot;)&quot;);

 // Output from the tests is not available until
 // the YAHOO.Test.Runner is done running the suite
 selenium.waitForCondition(&quot;!&quot; + browser_bot + &quot;.isRunning()&quot;, &quot;10000&quot;);
 String output = selenium.getEval(&quot;dom=getYUITestResults(&quot; + browser_bot + &quot;)&quot;);

 JSONObject results = JSONObject.fromObject(output);
 JSONObject test_case = results.getJSONObject(&quot;jsTestCase&quot;);
 JSONArray testCasePropertyNames = test_case.names();
 Iterator itr = testCasePropertyNames.iterator();

 /*
 * From the output, build an array with the following:
 * Test file
 * Test name
 * status (result)
 * message
 */
 while(itr.hasNext()) {
 String name = (String)itr.next();
 if(name.startsWith(&quot;test&quot;)) {
 JSONObject testResult = test_case.getJSONObject(name);
 String test_name = testResult.getString(&quot;name&quot;);
 String test_result = testResult.getString(&quot;result&quot;);
 String test_message = testResult.getString(&quot;message&quot;);
 Object[] testResultObject = {aBrowser.getCommand(), page_name, test_name, test_result, test_message};
 testResults.add(testResultObject);
 }
 }
 }
 } finally {
 // If an exception is thrown, this will guarantee that the selenium instance
 // is shut down properly
 selenium.stop();
 selenium = null;
 }
 return testResults;
}

/**
 * Inspects each test result and fails if the testResult was not &quot;pass&quot;
 */
@Test
public void inspectTestResults() {
 if(!this.testResult.equalsIgnoreCase(&quot;pass&quot;)) {
 fail(String.format(MESSAGE_FORMAT, this.browser, this.pageName, this.testName, this.message));
 }
}
</code></pre>

blocks|key|5254310|text|有一个新项目允许您在Java环境(如Ant)中运行QUnit测试，因此您可以将客户端测试套件与其他单元测试完全集成。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5254311|http://qunit-test-runner.googlecode.com|5254312|我已经用它对jQuery插件、objx代码、定制的OO+JavaScript进行了单元测试，它无需修改就可以做任何事情。|5254313|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.jquery.com/Qunit|1|http://qunit-test-runner.googlecode.com/|2|http://objx.googlecode.com/^0|P|5|0|0|0|13|1|0|F|4|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

There's a new project that lets you run <a href="http://docs.jquery.com/Qunit" rel="nofollow noreferrer">QUnit</a> tests in a Java environment (like Ant) so you can fully integrate your client-side test suite with your other unit tests.
<a href="http://qunit-test-runner.googlecode.com" rel="nofollow noreferrer">http://qunit-test-runner.googlecode.com</a>
I've used it to unit test jQuery plugins, <a href="http://objx.googlecode.com" rel="nofollow noreferrer">objx</a> code, custom OO JavaScript and it works for everything without modification.

blocks|key|3843882|text|我正在做的项目使用Js-Test-Driver在Chrome10和Jasmine-JSTD-Adapter上托管Jasmine，包括使用JS-Test-Driver中包含的code+coverage测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3843883|虽然每次我们在CI+environment上更改或更新浏览器时都会出现一些问题，但Jasmine测试运行得相当顺利，只有异步测试的小问题，但据我所知，这些问题可以使用Jasmine+Clock解决，但我还没有机会对它们进行修补。|3843884|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/js-test-driver/|1|https://github.com/ibolmo/jasmine-jstd-adapter|2|http://pivotal.github.com/jasmine/|3|http://code.google.com/p/js-test-driver/wiki/CodeCoverage|4|http://en.wikipedia.org/wiki/Continuous_integration^0|9|E|0|X|K|1|1K|7|2|2E|D|3|0|7|E|4|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]|$A|12|B|13|1|14]|$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|F|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]|R|$5|I|J|K|C|$L|S]]|T|$5|I|J|K|C|$L|U]]]]

The project I'm working on uses <a href="http://code.google.com/p/js-test-driver/" rel="nofollow noreferrer">Js-Test-Driver</a> hosting <a href="http://pivotal.github.com/jasmine/" rel="nofollow noreferrer">Jasmine</a> on Chrome 10 with <a href="https://github.com/ibolmo/jasmine-jstd-adapter" rel="nofollow noreferrer">Jasmine-JSTD-Adapter</a> including making use of <a href="http://code.google.com/p/js-test-driver/wiki/CodeCoverage" rel="nofollow noreferrer">code coverage</a> tests included in JS-Test-Driver.
While there are some problems each time we change or update browsers on the <a href="http://en.wikipedia.org/wiki/Continuous_integration" rel="nofollow noreferrer">CI environment</a> the Jasmine tests are running pretty smoothly with only minor issues with ansynchronous tests, but as far as I'm aware these can be worked around using Jasmine Clock, but I haven't had a chance to patch them yet.

blocks|key|5254415|text|我已经发布了用于验证依赖于浏览器的JavaScript测试的a+little+library，而不必使用浏览器。它是一个使用zombie.js加载测试页面并检查结果的Node.js模块。我已经在on+my+blog上写过了。下面是自动化的样子：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5254416|var+browsertest+=+require('../browsertest.js').browsertest;

describe('browser+tests',+function+()+{

++++it('should+properly+report+the+result+of+a+mocha+test+page',+function+(done)+{
++++++++browsertest({
++++++++++++url:+"file:///home/liam/work/browser-js-testing/tests.html",
++++++++++++callback:+function()+{
++++++++++++++++done();
++++++++++++}
++++++++});
++++});

});|code-block|syntax|javascript|5254417|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/liammclennan/browsertest|1|http://hackingon.net/post/Testing-Browser-dependent-JavaScript.aspx^0|U|G|0|2P|A|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

I've published <a href="https://github.com/liammclennan/browsertest" rel="nofollow noreferrer">a little library</a> for verifying browser-dependent JavaScript tests without having to use a browser. It is a Node.js module that uses zombie.js to load the test page and inspect the results. I've wrote about it <a href="http://hackingon.net/post/Testing-Browser-dependent-JavaScript.aspx" rel="nofollow noreferrer">on my blog</a>. Here is what the automation looks like:
<pre><code>var browsertest = require('../browsertest.js').browsertest;

describe('browser tests', function () {

 it('should properly report the result of a mocha test page', function (done) {
 browsertest({
 url: &quot;file:///home/liam/work/browser-js-testing/tests.html&quot;,
 callback: function() {
 done();
 }
 });
 });

});
</code></pre>

blocks|key|3844243|text|我查看了您的问题日期，当时有一些很好的JavaScript测试库和框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3844244|今天，你可以在不同的关注点找到更多的东西，比如TDD，BDD，Assetion和有/没有runners支持。|offset|length|3844245|在这个游戏中有很多玩家，像Mocha，Chai，QUnit，Jasmine等等。|3844246|你可以在this博客上找到更多关于JavaScript、移动设备和web测试的信息……|3844247|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Test-driven_development|1|https://en.wikipedia.org/wiki/Behavior-driven_development|2|https://en.wikipedia.org/wiki/Mocha_(JavaScript_framework))|3|https://en.wikipedia.org/wiki/List_of_unit_testing_frameworks#JavaScript|4|https://code.jquery.com/qunit/|5|https://en.wikipedia.org/wiki/Jasmine_(JavaScript_testing_framework))|6|http://catjs.blogspot.co.il/^0|0|N|3|0|R|3|1|0|D|5|2|J|4|3|O|5|4|U|7|5|0|4|4|6|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@$D|15|E|16|1|17]|$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]|$D|1F|E|1G|1|1H]|$D|1I|E|1J|1|1K]|$D|1L|E|1M|1|1N]]|A|$]]|$1|H|3|I|5|6|7|1O|8|@]|9|@$D|1P|E|1Q|1|1R]]|A|$]]|$1|J|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]|T|$5|M|N|O|A|$P|U]]|V|$5|M|N|O|A|$P|W]]|X|$5|M|N|O|A|$P|Y]]|Z|$5|M|N|O|A|$P|10]]|11|$5|M|N|O|A|$P|12]]]]

I looked on your question date and back then there were a few good JavaScript testing libraries and frameworks.
Today you can find much more and in different focus like <a href="https://en.wikipedia.org/wiki/Test-driven_development" rel="nofollow noreferrer">TDD</a>, <a href="https://en.wikipedia.org/wiki/Behavior-driven_development" rel="nofollow noreferrer">BDD</a>, Assetion and with/without runners support.
There are many players in this game, like <a href="https://en.wikipedia.org/wiki/Mocha_(JavaScript_framework)" rel="nofollow noreferrer">Mocha</a>, <a href="https://en.wikipedia.org/wiki/List_of_unit_testing_frameworks#JavaScript" rel="nofollow noreferrer">Chai</a>, <a href="https://code.jquery.com/qunit/" rel="nofollow noreferrer">QUnit</a>, <a href="https://en.wikipedia.org/wiki/Jasmine_(JavaScript_testing_framework)" rel="nofollow noreferrer">Jasmine</a>, etc...
You can find some more information in <a href="http://catjs.blogspot.co.il/" rel="nofollow noreferrer">this</a> blog about JavaScript, mobile, and web testing...

blocks|key|5253929|text|另一个可以与Ant一起运行的JavaScript测试框架是CrossCheck。在项目的构建文件中有一个通过Ant运行CrossCheck的示例。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5253930|CrossCheck尝试模拟浏览器，包括模拟样式的XMLHttpRequest和timeout/interval，但只取得了有限的成功。|5253931|不过，它目前还不能处理从网页加载JavaScript。您必须指定要加载和测试的JavaScript文件。如果您将所有的JavaScript代码与HTML分开，那么它可能对您有效。|5253932|entityMap|0|LINK|mutability|MUTABLE|url|https://dev.thefrontside.net/crosscheck|1|https://en.wikipedia.org/wiki/XMLHttpRequest^0|T|A|0|0|P|E|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Another JavaScript testing framework that can be run with Ant is <a href="https://dev.thefrontside.net/crosscheck" rel="nofollow noreferrer">CrossCheck</a>. There's an example of running CrossCheck via Ant in the build file for the project.
CrossCheck attempts, with limited success, to emulate a browser, including mock-style implementations of <a href="https://en.wikipedia.org/wiki/XMLHttpRequest" rel="nofollow noreferrer">XMLHttpRequest</a> and timeout/interval.
It does not currently handle loading JavaScript from a web page, though. You have to specify the JavaScript files that you want to load and test. If you keep all of your JavaScript code separated from your HTML, it might work for you.

blocks|key|2999795|text|我已经编写了一个Ant任务，它使用PhantomJS+(一种无头WebKit浏览器)在QUnit构建过程中运行Ant测试文件。如果任何测试失败，它也可能使构建失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2999796|https://github.com/philmander/ant-jstestrunner|2999797|entityMap|0|LINK|mutability|MUTABLE|url|http://phantomjs.org/|1|https://en.wikipedia.org/wiki/WebKit|2^0|H|9|0|W|6|1|0|0|1A|2|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]|$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|E]]]]

I've written an Ant task which uses <a href="http://phantomjs.org/" rel="nofollow noreferrer">PhantomJS</a>, a headless <a href="https://en.wikipedia.org/wiki/WebKit" rel="nofollow noreferrer">WebKit</a> browser, to run QUnit HTML test files within an Ant build process. It can also fail the build if any tests fail.
<a href="https://github.com/philmander/ant-jstestrunner" rel="nofollow noreferrer">https://github.com/philmander/ant-jstestrunner</a>

blocks|key|753045|text|这是对几个测试工具的很好的评估。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|753046|JavaScript+unit+test+tools+for+TDD|offset|length|753047|我个人更喜欢https://code.google.com/p/js-test-driver/|753048|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/300855/looking-for-a-better-javascript-unit-test-tool|1|https://code.google.com/p/js-test-driver/^0|0|0|Y|0|0|6|15|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

This is a good evaluation of several testing tools.

<a href="https://stackoverflow.com/questions/300855/looking-for-a-better-javascript-unit-test-tool">JavaScript unit test tools for TDD</a>

I personally prefer 
<a href="https://code.google.com/p/js-test-driver/" rel="nofollow noreferrer">https://code.google.com/p/js-test-driver/</a>

I'm trying to incorporate some JavaScript unit testing into my automated build process. Currently JSUnit works well with JUnit, but it seems to be abandonware and lacks good support for Ajax, debugging, and timeouts.
Has anyone had any luck automating (with <a href="https://en.wikipedia.org/wiki/Apache_Ant" rel="nofollow noreferrer">Ant</a>) a unit testing library such as <a href="https://en.wikipedia.org/wiki/Yahoo!_UI_Library" rel="nofollow noreferrer">YUI</a> test, jQuery's <a href="https://code.jquery.com/qunit/" rel="nofollow noreferrer">QUnit</a>, or <a href="http://code.google.com/p/jqunit/" rel="nofollow noreferrer">jQUnit</a>?
Note: I use a custom built Ajax library, so the problem with Dojo's DOH is that it requires you to use their own Ajax function calls and event handlers to work with any Ajax unit testing.

Automated unit testing with JavaScript

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在尝试将一些JavaScript单元测试整合到我的自动化构建过程中。目前，JSUnit可以很好地与JUnit一起工作，但它似乎是被遗弃的软件，并且缺乏对Ajax、调试和超时的良好支持。有没有人有幸(用)自动化了单元测试库，如测试、jQuery的或注意:我使用的是定制的Ajax库，因此Dojo的DOH的问题在于，它要求您使用自己的Ajax函数调用和事件处理程序来处理任何Ajax单元测试。

问使用JavaScript进行自动化单元测试
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用JavaScript进行自动化单元测试EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用JavaScript进行自动化单元测试
EN