You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2022. It is now read-only.
For some time I'm trying to get my app working with karma-closure, unsuccessfully. Files seem to load, there are no errors even on debug setting, yet still no tests run and karma fails.
To finally find what is the proper karma.conf.js I turned to the example, and after adding a minimal package json (which is missing)
Chrome 44.0.2403 (Linux 0.0.0) ERROR: 'goog.require could not find: main'
Chrome 44.0.2403 (Linux 0.0.0) ERROR
Uncaught Error: goog.require could not find: main
at karma-closure/test-app/lib/goog/base.js:353
So it seems the example app doesn't seem to work either.
My main app setup is:
// Karma configuration
// Generated on Sat Aug 08 2015 20:45:45 GMT+0200 (CEST)
module.exports = function(config) {
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: __dirname,
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: [
'jasmine',
'jasmine-matchers',
'closure'
],
// list of files / patterns to load in the browser
files: [
// closure base
'bower_components/closure-library/closure/goog/base.js',
// included files - tests
'app/src/**/*_test.js',
// source files - these are only watched and served
{pattern: 'app/src/**/*!(_test).js', included: false},
// external deps
{pattern: 'bower_components/closure-library/closure/goog/deps.js', included: false, served: false}
],
// list of files to exclude
exclude: [
'bower_components/closure-library/closure/goog/**/*_test.js'
],
preprocessors: {
'app/src/**/*_test.js': ['closure', 'closure-iit'],
'app/src/**/*!(_test).js': ['closure', 'coverage'],
'bower_components/closure-library/closure/goog/deps.js': ['closure-deps']
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['nyan', 'coverage'],
// web server port
port: 9876,
// enable / disable colors in the output (reporters and logs)
colors: true,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_DEBUG,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: false,
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: ['Chrome'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: true
});
};
I have the same issue. I've narrowed this down to the fact that the file_list_modified event wont fire a files promise in Protractor 0.13.0 anymore, but simply resolves the files directly. Simply removing the excess seemed to fix it. I can prepare a pull request tomorrow if the dev's are ok with that.
For some time I'm trying to get my app working with karma-closure, unsuccessfully. Files seem to load, there are no errors even on debug setting, yet still no tests run and karma fails.
To finally find what is the proper
karma.conf.js
I turned to the example, and after adding a minimal package json (which is missing)i runned
karma start karma.conf.js
just to seeSo it seems the example app doesn't seem to work either.
My main app setup is:
and the result is
The text was updated successfully, but these errors were encountered: