integrated event scrubbing with direct image access - need to clean up code

1 files changed, 71 insertions, 0 deletions

diff --git a/www/lib/angular-carousel/test/karma.conf.js b/www/lib/angular-carousel/test/karma.conf.js
new file mode 100644
index 00000000..00f32b69
--- /dev/null
+++ b/www/lib/angular-carousel/test/karma.conf.js
@@ -0,0 +1,71 @@
+var grunt = require('grunt');
+module.exports = function ( karma ) {
+  karma.set({
+    /**
+     * From where to look for files, starting with the location of this file.
+     */
+    basePath: './..',
+
+    /**
+     * This is the list of file patterns to load into the browser during testing.
+     */
+    files: [
+        'bower_components/angular/angular.js',
+        'bower_components/angular-touch/angular-touch.js',
+        'bower_components/angular-mocks/angular-mocks.js',
+        'bower_components/requirejs/require.js',
+        'dist/angular-carousel.js',
+        'test/unit/*.js'
+    ],
+
+    frameworks: [ 'jasmine' ],
+    plugins: [ 'karma-jasmine', 'karma-firefox-launcher', 'karma-chrome-launcher', 'karma-coverage'],
+
+    logLevel:  'DEBUG',
+    /**
+     * How to report, by default.
+     */
+    reporters: ['dots', 'coverage'],
+
+    preprocessors: {
+      // source files, that you wanna generate coverage for
+      // do not include tests or libraries
+      // (these files will be instrumented by Istanbul)
+      '../dist/*.js': ['coverage']
+    },
+
+    coverageReporter: {
+      type : 'html',
+      dir : 'coverage/'
+    },
+
+    /**
+     * On which port should the browser connect, on which port is the test runner
+     * operating, and what is the URL path for the browser to use.
+     */
+    port: 7018,
+    runnerPort: 7100,
+    urlRoot: '/',
+
+    /**
+     * Disable file watching by default.
+     */
+    autoWatch: false,
+
+    /**
+     * The list of browsers to launch to test ondest     * default, but other browser names include:
+     * Chrome, ChromeCanary, Firefox, Opera, Safari, PhantomJS
+     *
+     * Note that you can also use the executable name of the browser, like "chromium"
+     * or "firefox", but that these vary based on your operating system.
+     *
+     * You may also leave this blank and manually navigate your browser to
+     * http://localhost:9018/ when you're running tests. The window/tab can be left
+     * open and the tests will automatically occur there during the build. This has
+     * the aesthetic advantage of not launching a browser every time you save.
+     */
+    browsers: [
+      'Chrome'
+    ]
+  });
+};