From e3c9f185b7f3d5fcab1a4eb035d6421587c6e460 Mon Sep 17 00:00:00 2001 From: Adam Shaw Date: Sat, 22 Mar 2014 11:41:32 -0700 Subject: [PATCH] move karma-related dependencies into the repo. use karma-cli --- package.json | 5 ++++- readme.md | 4 ++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/package.json b/package.json index 79c9a77..a122af9 100644 --- a/package.json +++ b/package.json @@ -15,7 +15,10 @@ "grunt-contrib-clean": "~0.4.0", "grunt-contrib-jshint": "~0.8.0", "grunt-jscs-checker": "~0.3.2", - "lumbar": "~2.0.0-beta19" + "lumbar": "~2.0.0-beta19", + "karma": "^0.12.1", + "karma-jasmine": "^0.2.2", + "karma-phantomjs-launcher": "^0.1.2" }, "scripts": { "install": "bower install" diff --git a/readme.md b/readme.md index 279f898..2e27523 100644 --- a/readme.md +++ b/readme.md @@ -48,9 +48,9 @@ If you want to clean up the generated files, run: Automated Testing ----------------- -To run automated tests, you must first install [karma] globally, as well as some karma plugins: +To run automated tests, you must first install [karma] command line utility: - npm install -g karma karma-jasmine karma-phantomjs-launcher + npm install -g karma-cli Then, assuming all your source files have been built (via `grunt dev` or `watch`), you can run the tests from a browser: