BUG: Tests are failing with Google Chrome Version 76.0.3809.100

Expected behaviour

The unit tests are running successfully

Actual behaviour

The unit tests failing

Environment Details

Windows 10 Google Chrome Version 76.0.3809.100 package.json

{
    "angular": "^1.7.8",
    "karma": "^4.2.0",
    "karma-chrome-launcher": "^3.0.0",
    "karma-coverage": "^1.1.1",
    "karma-jasmine": "^2.0.1",
    "karma-jasmine-html-reporter": "^1.4.2",
    "karma-junit-reporter": "^1.1.0",
    "karma-ng-html2js-preprocessor": "^1.0.0",
    "karma-spec-reporter": "0.0.32"
}

Log

##[section]Starting: gulp testonce
==============================================================================
Task         : Gulp
Description  : Node.js streaming task based build system
Version      : 0.141.2
Author       : Microsoft Corporation
Help         : [More Information](https://go.microsoft.com/fwlink/?LinkID=613721)
==============================================================================
[command]C:\Program Files\nodejs\node.exe C:\vsts\build\_work\1\s\App.Web\node_modules\gulp\bin\gulp.js testonce --gulpfile C:\vsts\build\_work\1\s\App.Web\gulpfile.js
[14:49:07] Using gulpfile C:\vsts\build\_work\1\s\App.Web\gulpfile.js
[14:49:07] Starting 'testonce'...
[14:49:08] Finished 'testonce' after 1.07 s
09 08 2019 14:49:10.316:INFO [karma-server]: ‌Karma v4.2.0 server started at http://0.0.0.0:9876/‌
09 08 2019 14:49:10.316:INFO [launcher]: ‌Launching browsers ChromeHeadless with concurrency unlimited‌
09 08 2019 14:49:10.332:INFO [launcher]: ‌Starting browser ChromeHeadless‌
09 08 2019 14:49:11.266:INFO [HeadlessChrome 76.0.3809 (Windows 10.0.0)]: ‌Connected on socket n2N5DrcsFF2BU453AAAA with id 74774773‌

  maps component
    initializeComponent
      ‌× ‌WHEN the component is initialized‌
            AND the model already contains data
            THEN this data should be displayed in the banner‌ (17ms)‌
	Error: [$injector:unpr] Unknown provider: rxMapsDirectiveProvider <- rxMapsDirective
	https://errors.angularjs.org/1.7.8/$injector/unpr?p0=rxMapsDirectiveProvider%20%3C-%20rxMapsDirective
	    at node_modules/angular/angular.js:138:12
	    at node_modules/angular/angular.js:4924:19
	    at Object.getService [as get] (node_modules/angular/angular.js:5084:32)
	    at node_modules/angular/angular.js:4929:45
	    at Object.getService [as get] (node_modules/angular/angular.js:5084:32)
	    at $componentController (node_modules/angular-mocks/angular-mocks.js:2593:34)
	    at UserContext.<anonymous> (src/shared/components/rx-maps/tests/rx-maps.component.test.js:242:26)
	    at <Jasmine>

      ‌× ‌WHEN the component is initialized‌
            THEN the bound model should be set as the correct location‌ (3ms)‌
	Error: [$injector:unpr] Unknown provider: rxMapsDirectiveProvider <- rxMapsDirective
	https://errors.angularjs.org/1.7.8/$injector/unpr?p0=rxMapsDirectiveProvider%20%3C-%20rxMapsDirective
	    at node_modules/angular/angular.js:138:12
	    at node_modules/angular/angular.js:4924:19
	    at Object.getService [as get] (node_modules/angular/angular.js:5084:32)
	    at node_modules/angular/angular.js:4929:45
	    at Object.getService [as get] (node_modules/angular/angular.js:5084:32)
	    at $componentController (node_modules/angular-mocks/angular-mocks.js:2593:34)
	    at UserContext.<anonymous> (src/shared/components/rx-maps/tests/rx-maps.component.test.js:88:26)
	    at <Jasmine>

Steps to fix the behaviour

1. Downgrade Google Chrome to Version 75.0.3770.80
2. Rerun tests

I don’t know what was changed in Google Chrome. But it causes problems on every computer. The biggest problem is that Google updates itself automatically on the build system. Do you have any idea why? I’m looking forward to a solution. Thanks a lot 😃

[tobiasbenkner]

not really. we have found different solutions that could help.

1. wait for version 78. Everything works again. it will be released on 22 oct 2019. https://www.chromestatus.com/features/schedule

2. we don’t have bundling in the project. We load several thousand files in the tests. Chrome doesn’t seem to be able to handle it. now we are introduce webpack for this issue. before the bundle karma run a different amount of tests. now the amount of tests are constant. but the amount of failing tests are different in every run.

• and more developer are complaining about the chrome version 76. see https://support.google.com/chrome/thread/11775763?hl=en

[junqdu]

currently our unit tests also fail to execute, and it seems like we can either wait for v78 comes out or move to Webpack.