Index: third_party/qunit/README.chromium |
diff --git a/third_party/qunit/README.chromium b/third_party/qunit/README.chromium |
new file mode 100644 |
index 0000000000000000000000000000000000000000..ef2df60727ab7b36f7ea9bb4766e4daf664c91ee |
--- /dev/null |
+++ b/third_party/qunit/README.chromium |
@@ -0,0 +1,32 @@ |
+Name: QUnit |
+Short Name: QUnit |
+URL: https://github.com/jquery/qunit |
+Version: 1.14.0 |
+License: MIT |
+Security Critical: no |
+ |
+Description: |
+QUnit is a powerful, easy-to-use, JavaScript unit testing framework. It's used |
+by the jQuery project to test its code and plugins but is capable of testing any |
+generic JavaScript code (and even capable of testing JavaScript code on the |
+server-side). |
+ |
+QUnit is especially useful for regression testing: Whenever a bug is reported, |
+write a test that asserts the existence of that particular bug. Then fix it and |
+commit both. Every time you work on the code again, run the tests. If the bug |
+comes up again - a regression - you'll spot it immediately and know how to fix |
+it, because you know what code you just changed. |
+ |
+Having good unit test coverage makes safe refactoring easy and cheap. You can |
+run the tests after each small refactoring step and always know what change |
+broke something. |
+ |
+QUnit is similar to other unit testing frameworks like JUnit, but makes use of |
+the features JavaScript provides and helps with testing code in the browser, |
+e.g. with its stop/start facilities for testing asynchronous code. |
+ |
+It is currently used by the chrome remote desktop team for JavaScript unit |
+testing. |
+ |
+Local Modifications: |
+None |