summaryrefslogtreecommitdiff
path: root/www/crm/wp-content/plugins/civicrm/civicrm/bower_components/qunit/addons/step/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'www/crm/wp-content/plugins/civicrm/civicrm/bower_components/qunit/addons/step/README.md')
-rw-r--r--www/crm/wp-content/plugins/civicrm/civicrm/bower_components/qunit/addons/step/README.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/www/crm/wp-content/plugins/civicrm/civicrm/bower_components/qunit/addons/step/README.md b/www/crm/wp-content/plugins/civicrm/civicrm/bower_components/qunit/addons/step/README.md
new file mode 100644
index 00000000..37af9df6
--- /dev/null
+++ b/www/crm/wp-content/plugins/civicrm/civicrm/bower_components/qunit/addons/step/README.md
@@ -0,0 +1,18 @@
+QUnit.step() - A QUnit Addon For Testing execution in order
+============================================================
+
+This addon for QUnit adds a step method that allows you to assert
+the proper sequence in which the code should execute.
+
+Example:
+
+ test("example test", function () {
+ function x() {
+ QUnit.step(2, "function y should be called first");
+ }
+ function y() {
+ QUnit.step(1);
+ }
+ y();
+ x();
+ }); \ No newline at end of file