search

karma-runner / karma-ie-launcher

A Karma plugin. Launcher for Internet Explorer.
MIT License
59 stars 23 forks source link

IE starts but it just idles #7

Open hyusetiawan opened 11 years ago

hyusetiawan commented 11 years ago

My Environment:

Windows 7 32-Bit IE version 10 VM: VirtualBox Node: 0.10.18

here is my karma.conf.js:

// Karma configuration
// Generated on Thu Sep 12 2013 18:32:23 GMT-0700 (PDT)

module.exports = function (config) {
    config.set({

        // base path, that will be used to resolve files and exclude
        basePath: '',

        // frameworks to use
        frameworks: ['jasmine', 'requirejs'],

        // list of files / patterns to load in the browser
        files: [
            {pattern: 'bases/**', included: false},
            {pattern: 'models/**', included: false},
            {pattern: 'components/**', included: false},
            {pattern: 'libs/**', included: false},
            {pattern: 'tests/**', included: false},
            {pattern: 'configs/base.js', included: false},
            'configs/test.js',
            'tests/jquery.jasmine.js'
        ],
        // list of files to exclude
        /*
         exclude coffeescript mapping files, because karma will include the .map files (look at file pattern above)
         and try to execute them as JS, so we manually exclude them here
         */
        exclude: [
            '*.map',
            '*/*.map',
            '*/*/*.map',
            '*/*/*/*.map'
        ],

        // test results reporter to use
        // possible values: 'dots', 'progress', 'junit', 'growl', 'coverage'
        reporters: ['progress'],

        // 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_INFO,

        // enable / disable watching file and executing tests whenever any file changes
        autoWatch: true,

        // Start these browsers, currently available:
        // - Chrome
        // - ChromeCanary
        // - Firefox
        // - Opera
        // - Safari (only Mac)
        // - PhantomJS
        // - IE (only Windows)
        browsers: ['IE'],

        // If browser does not capture in given timeout [ms], kill it
        captureTimeout: 60000,
        // Continuous Integration mode
        // if true, it capture browsers, run tests and exit
        singleRun: false
    });
};

and this is the screenshot how it looks like:

00000002

It sits there idle without executing any test, I see no errors too. All 11 tests run fine on Mac for Chrome, PhantomJS etc.

I am not sure where to begin in debugging this, any hints I can follow?

hyusetiawan commented 11 years ago

one update clicking Debug will yield an error like this:

SCRIPT438: Object doesn't support property or method 'start' debug.html, line 35 character 9

I am not sure if that helps

b1r3k commented 10 years ago

I'm was experiencing similar problem. Try to define Chrome as first browser and check if everything works. I've also set paths to browsers manually through env variables.

noresjo commented 10 years ago

I had this issue. As a workaround I tried @b1r3k 's fix of moving IE to after Chrome in the config file. This removed the problem. Can we solve this in a more permanent way though?

noresjo commented 10 years ago

Update: I have this in a CI environment with Teamcity. On 3/5 agents machines things work ok. On 2 of them "It sits there idle without executing any test, I see no errors too.". The machines are very similiar (should be identical) but I realise something is most likely different on the agents. Can't think of what though.... Sigh.

sylvain-hamel commented 10 years ago

@noresjo can you still reproduce this bug with the latest version?

mcfung commented 10 years ago

Hi all,

I am new to Karma and I am suffering from similar problem. I am not sure should I post a new issue or comment on this issue. I have set up a new nightly Jenkins job which check out the latest code and run karma start. Every morning it hangs with the following logs.. when I abort it and then build it again it passes.

The Tomcat is started automatically when the machine start up, when it's executing the Karma, I cannot see any browser launches. Therefore I cannot debug the script on the browser.

May I ask if there is anything wrong in my setup?

My environment is as follows:

Windows 7 64-Bit IE version 8 node 0.10.26 karma 0.10 karma-ie-launcher 0.1.5 Jenkins ver. 1.556

Log

[32mINFO [karma]: Karma v0.10.10 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [launcher]: Starting browser Firefox
INFO [launcher]: Starting browser IE
INFO [IE 8.0.0 (Windows 7)]: Connected on socket oitihogBkMuiEkmodx3o
INFO [Firefox 29.0.0 (Windows 7)]: Connected on socket aDW5aolColcYIiXmdx3p
INFO [Chrome 35.0.1916 (Windows 7)]: Connected on socket XYCoBFjwn7UxxMHXdx3n
Firefox 29.0.0 (Windows 7) LOG: 'Please enable jatt'
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 1 of 0 SUCCESS (0 secs / 0.005 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 2 of 0 SUCCESS (0 secs / 0.007 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 3 of 0 SUCCESS (0 secs / 0.015 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 4 of 0 SUCCESS (0 secs / 0.02 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 5 of 0 SUCCESS (0 secs / 0.026 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 6 of 0 SUCCESS (0 secs / 0.031 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 7 of 0 SUCCESS (0 secs / 0.038 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 8 of 0 SUCCESS (0 secs / 0.042 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 9 of 0 SUCCESS (0 secs / 0.065 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 10 of 0 SUCCESS (0 secs / 0.081 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 11 of 0 SUCCESS (0 secs / 0.094 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 12 of 0 SUCCESS (0 secs / 0.108 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 13 of 0 SUCCESS (0 secs / 0.122 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
WARN [web-server]: 404: /ekp/servlet/ekp/TEACHREVIEW
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 14 of 0 SUCCESS (0 secs / 0.148 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 15 of 0 SUCCESS (0 secs / 0.152 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 16 of 0 SUCCESS (0 secs / 0.155 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 17 of 0 SUCCESS (0 secs / 0.19 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 18 of 0 SUCCESS (0 secs / 0.222 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 19 of 0 SUCCESS (0 secs / 0.245 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 1 of 0 SUCCESS (0 secs / 0.017 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 2 of 0 SUCCESS (0 secs / 0.022 secs)
Chrome 35.0.1916 (Windows 7) LOG: 'Please enable jatt'
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 2 of 0 SUCCESS (0 secs / 0.022 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 3 of 0 SUCCESS (0 secs / 0.023 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 4 of 0 SUCCESS (0 secs / 0.024 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 5 of 0 SUCCESS (0 secs / 0.034 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 6 of 0 SUCCESS (0 secs / 0.038 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 7 of 0 SUCCESS (0 secs / 0.041 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 20 of 0 SUCCESS (0 secs / 0.267 secs)
Chrome 35.0.1916 (Windows 7): Executed 8 of 0 SUCCESS (0 secs / 0.045 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 21 of 0 SUCCESS (0 secs / 0.306 secs)
Chrome 35.0.1916 (Windows 7): Executed 8 of 0 SUCCESS (0 secs / 0.045 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 21 of 0 SUCCESS (0 secs / 0.306 secs)
Chrome 35.0.1916 (Windows 7): Executed 9 of 0 SUCCESS (0 secs / 0.064 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 21 of 0 SUCCESS (0 secs / 0.306 secs)
Chrome 35.0.1916 (Windows 7): Executed 10 of 0 SUCCESS (0 secs / 0.079 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 21 of 0 SUCCESS (0 secs / 0.306 secs)
Chrome 35.0.1916 (Windows 7): Executed 11 of 0 SUCCESS (0 secs / 0.088 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 21 of 0 SUCCESS (0 secs / 0.306 secs)
Chrome 35.0.1916 (Windows 7): Executed 12 of 0 SUCCESS (0 secs / 0.098 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 22 of 0 SUCCESS (0 secs / 0.353 secs)
Chrome 35.0.1916 (Windows 7): Executed 12 of 0 SUCCESS (0 secs / 0.098 secs)
WARN [web-server]: 404: /ekp/servlet/ekp/TEACHREVIEW
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 22 of 0 SUCCESS (0 secs / 0.353 secs)
Chrome 35.0.1916 (Windows 7): Executed 13 of 0 SUCCESS (0 secs / 0.108 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 22 of 0 SUCCESS (0 secs / 0.353 secs)
Chrome 35.0.1916 (Windows 7): Executed 14 of 0 SUCCESS (0 secs / 0.132 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Firefox 29.0.0 (Windows 7): Executed 22 of 0 SUCCESS (0 secs / 0.353 secs)
Chrome 35.0.1916 (Windows 7): Executed 15 of 0 SUCCESS (0 secs / 0.134 secs)
IE 8.0.0 (Windows 7): Executed 0 of 0 SUCCESS (0 secs / 0 secs)

karma.conf.js

module.exports = function(config) {
    config
        .set({

                 // base path, that will be used to resolve files and exclude
                 basePath: '',

                 // frameworks to use
                 frameworks: ['qunit', 'sinon', 'requirejs'],

                 // list of files / patterns to load in the browser
                 files: [

                     'test/js/test-main.js',

                     {pattern: 'test/js/**/*.spec.js', included: false},
                     {pattern: 'test/js/**/*.spec.coffee', included: false}
                 ],

                 // list of files to exclude
                 exclude: [

                 ],

                 preprocessors: {
                     '**/*.html': 'html2js',
                     '**/*.coffee': 'coffee'
                 },

                 // test results reporter to use
                 // possible values: 'dots', 'progress', 'junit', 'growl', 'coverage'
                 reporters: ['progress', 'junit', 'coverage'],
                 junitReporter: {

                     outputFile: 'target/reports/test-results/js-test-results.xml'
                 },
                 coverageReporter: {
                     type: 'cobertura',
                     dir: 'target/reports/test-results/'
                 },

                 // 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_INFO,

                 // enable / disable watching file and executing tests whenever any file changes
                 autoWatch: false,

                 // Start these browsers, currently available:
                 // - Chrome
                 // - ChromeCanary
                 // - Firefox
                 // - Opera (has to be installed with `npm install karma-opera-launcher`)
                 // - Safari (only Mac; has to be installed with `npm install karma-safari-launcher`)
                 // - PhantomJS
                 // - IE (only Windows; has to be installed with `npm install karma-ie-launcher`)
                 browsers: ['Chrome', 'Firefox', 'IE'],

                 // If browser does not capture in given timeout [ms], kill it
                 captureTimeout: 60000,

                 // Continuous Integration mode
                 // if true, it capture browsers, run tests and exit
                 singleRun: true
             });
};

Thanks

sylvain-hamel commented 10 years ago

@mcfung, can you update to karma 0.12 and see if you still have this issue?

mcfung commented 10 years ago

@sylvain-hamel, thank you very much! With Karma 0.12 it can fail the build. However the IE is not running the tests and therefore the failure is false negative. I'll try to update the tolerance in karma.conf.js and see if it helps.

Thanks

joeloliver commented 8 years ago

I had the same problem and Its works for me: http://stackoverflow.com/questions/9618774/jenkins-selenium-gui-tests-are-not-visible-on-windows

Sayan751 commented 6 years ago

I am also facing the same problem, and none of the workarounds worked for me. In my case, it worked fine as long as the number of tests is small, like 20 something. However, with more tests IE slows down and eventually hangs and gets disconnected.