jasmine: Tests breaks after upgrading jasmine-core from 2.99.0 to 3.1.0

I submitted a pull request (karma-runner/karma-jasmine#192) to karma-jasmine a few weeks ago to add support for Jasmine 3.x, but it hasn’t seen attention from the maintainers there. We changed some of the mechanisms for reporting some errors in 3.0, so it might be related to that.

Hope this helps. Thanks for using Jasmine!

For those still having this issue I would suggest the following since most of the proposed answers here didn’t resolve the problem our team was facing.

• Run your tests and enable watch (i.e. watch=true) if disabled, and remove the “headless” flag (if included in your karma.conf.js file) if you are using it (you’ll need to see the console in the browser).

Someone suggested to look in the console for errors in a related post in stack overflow and I cannot stress enough how simple and helpful this is.

The issue for our team was that we are using a directive in a dummy component in our spec file, but the dummy component was missing the id for the resizeHandle in the directive, which is used to create an observable stream of mouse events (see below)

export class ResizableDirective implements AfterViewInit, OnDestroy { @Input('attr.resize-handle') private resizeHandle; private mouseUp$: Observable<MouseEvent | Event>; private mouseDown$: Observable<any>; private mouseMove$: Observable<MouseEvent | Event>; private subscription: Subscription;

constructor( @Inject(DOCUMENT) private document, private element: ElementRef, private renderer: Renderer2 ) { }

ngAfterViewInit() { this.mouseMove$ = fromEvent(this.document, 'mousemove'); this.mouseUp$ = fromEvent(this.document, 'mouseup'); this.mouseDown$ = fromEvent(this.resizeHandle, 'mousedown') .map((event: MouseEvent) => { event.stopPropagation(); const offset = this.calculateOffset(event); return this.mouseMove$.map((moveEvent: MouseEvent) => { moveEvent.stopPropagation(); moveEvent.preventDefault(); return this.calculatePosition(offset, moveEvent); }) .takeUntil(this.mouseUp$); }) .flatMap(_ => _); } }

The bold code above wound up throwing this error ⇓

{ "message": "An error was thrown in afterAll\n[object ErrorEvent]", "str": "An error was thrown in afterAll\n[object ErrorEvent]" }

So, the most logical and helpful answer is to look at the console in the browser because it will give you hints with the trace and call stack as to what could possibly be going wrong. Fixing the dummy component to include the “resizeHandle” fixed it being undefined and throwing the silent error, which was visible in the browser.

Also, it looks like as of v2.0.0 karma-jasmine fixes the obscure error thrown and possibly bubbles up a more useful error for those using an older version of karma-jasmine (like we were).

Hope this helps others find a path to resolving this error!

Cheers 🍺

To whom it may concern, we had a similar issue:

Chrome 70.0.3508 (Mac OS X 10.13.6) ERROR
  {
    "message": "An error was thrown in afterAll\n[object ErrorEvent]",
    "str": "An error was thrown in afterAll\n[object ErrorEvent]"
  }

problem was a test failing silently, which was ultimately found out by running Chrome with singleRun=false and checking the reports in the Jasmine UI.

For anyone who is still struggling even after trying proposed solutions on here (like me), this might be worth a check for you:

My tests were succeeding locally with no warnings or errors. When I pushed up to the remote, our CI server (Jenkins) was failing those tests and giving a terribly cryptic, awful error message that is listed above in the OPs comment. After 90 minutes or so of googling, I finally found my problem. I was using HttpClientModule in my imports for one of my tests. In ngOnInit() of the component I was testing, I was making service calls which were failing but giving me said terrible error message. When googling I saw a whole bunch of people proposing to upgrade/downgrade jasmine and that seemed to be the universal solution. After trying multiple proposed versions of jasmine, I did some more googling. I found one person at the very bottom of a thread suggesting to check for use of HttpClientModule in tests instead of HttpClientTestingModule. Sure enough I had 1 component.spec.ts out of like 75 importing HttpClientModule and it was failing my build and giving me that awful message without telling me which test failed. Pretty annoying. Still not sure why it worked locally but not on Jenkins.

Until there’s a new karma-jasmine version that supports some of the new features in Jasmine 3.0, there’s not much for us to look into here. I’m keeping this issue open in case there are some other issues that aren’t resolved by updating karma-jasmine.

Hope this helps. Thanks for using Jasmine!

@adisreyaj thanks for the answer! This helped a lot, because I had just switched to running headless Chrome to make things faster but it looks like a regular browser is needed for local development in order to find these weird test failures.

I see that same error message from @jahller. I’ve noticed it is somehow related to concurrency, because it does not happen in the same tests, every now and then all tests manage to pass, and the more tests, the more often it happens.

I’ve also noticed that when trying multiple browsers, IE breaks the most, almost always.

There was just a dependencies issues in my package.json I updated everything, (jasma core , karma , … ) , It’s working now. Sorry about that, thanks for your help

@ilancohen I changed few things :

• the angular.json of the project. For each libraries, I set up my test environment :

[...]
     "test": {
                    "builder": "@angular-devkit/build-angular:karma",
                    "options": {
                        "polyfills": "projects/my-lib/src/polyfills.ts",
                        "main": "projects/my-lib/src/test.ts",
                        "tsConfig": "projects/my-lib/tsconfig.spec.json",
                        "karmaConfig": "projects/my-lib/karma.conf.js"
                    }
                },
[...]

• tsconfig.spec.json of a specific project :

{
    "extends": "../../tsconfig.json",
    "compilerOptions": {
        "outDir": "../../out-tsc/spec",
        "types": [
            "jasmine",
            "node"
        ]
    },
    "files": [
        "src/test.ts",
        "src/polyfills.ts"
    ],
    "include": [
        "**/*.spec.ts",
        "**/*.d.ts"
    ]
}

• polyfills.ts of a specific project : I added this two lines to all polyfills I need to import.

import 'core-js/es7/reflect';
import 'zone.js/dist/zone';

I had the same issue with a library project with angular 6. And I fixed it with polyfills inside the karma.conf file of my project.

You maybe need to add this two lines :

import 'core-js/es7/reflect';
import 'zone.js/dist/zone';

My problem was caused by using “this.router.navigate([‘/login’]);” in ngOnInit method in completely other component. In your tests you need to specify:

                RouterTestingModule.withRoutes([
                    { path: 'login', component: LoginComponent }
                ]),

and put this formula into “imports”, and also “LoginComponent” into “declarations”.

Since the error message is rather obscure I don’t know if it helps here, but what helped in my case was removing test.js from the files section in karma,conf.js.

After also moving karma.conf.js to the /src folder and changing the path to this file in angular.json I got it to work with jasmine 3.1.0. This is also how it gets generated if you do ng new.

Im also getting this issue when running npm test 😦 all the unit test code in the *.spec files have been commented out for debug purpose… and I get this:

 10% building modules 1/1 modules 0 active16 05 2018 10:47:23.649:WARN [karma]: No captured browser, open http://localhost:9876/
16 05 2018 10:47:23.660:INFO [karma]: Karma v2.0.2 server started at http://0.0.0.0:9876/
16 05 2018 10:47:23.661:INFO [launcher]: Launching browser Chrome with unlimited concurrency
16 05 2018 10:47:23.668:INFO [launcher]: Starting browser Chrome
16 05 2018 10:47:30.338:WARN [karma]: No captured browser, open http://localhost:9876/  
16 05 2018 10:47:30.496:INFO [Chrome 66.0.3359 (Mac OS X 10.13.4)]: Connected on socket 4yMxIms1uAC0jI69AAAA with id 45005496
Chrome 66.0.3359 (Mac OS X 10.13.4) ERROR
  {
    "message": "An error was thrown in afterAll\n[object ErrorEvent]",
    "str": "An error was thrown in afterAll\n[object ErrorEvent]"
  }
Chrome 66.0.3359 (Mac OS X 10.13.4): Executed 0 of 0 ERROR (0 secs / 0 secs)
Chrome 66.0.3359 (Mac OS X 10.13.4) ERROR
  {
    "message": "An error was thrown in afterAll\n[object ErrorEvent]",
    "str": "An error was thrown in afterAll\n[object ErrorEvent]"
Chrome 66.0.3359 (Mac OS X 10.13.4): Executed 0 of 0 ERROR (0.013 secs / 0 secs)
^C
MacBook-Pro:fe user$ 

package.json

{
  "name": "project",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve --host 0.0.0.0 --proxy-config proxy.conf.json",
    "build": "ng build --prod --output-hashing none",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^5.0.0",
    "@angular/common": "^5.0.0",
    "@angular/compiler": "^5.0.0",
    "@angular/core": "^5.0.0",
    "@angular/forms": "^5.0.0",
    "@angular/http": "^5.0.0",
    "@angular/platform-browser": "^5.0.0",
    "@angular/platform-browser-dynamic": "^5.0.0",
    "@angular/router": "^5.0.0",
    "@types/jasmine": "^2.8.7",
    "bootstrap": "^4.1.1",
    "core-js": "^2.5.6",
    "karma-jasmine": "^1.1.2",
    "keycloak-js": "3.4.3",
    "lodash": "^4.17.10",
    "ng2-slim-loading-bar": "^4.0.0",
    "ng2-toastr": "^4.1.2",
    "ngx-bootstrap": "^2.0.5",
    "protractor": "^5.3.2",
    "rxjs": "^5.5.2",
    "svgxuse": "^1.2.6",
    "zone.js": "^0.8.14"
  },
  "devDependencies": {
    "@angular/cli": "1.7.2",
    "@angular/compiler-cli": "^5.0.0",
    "@angular/language-service": "^5.0.0",
    "@types/jasmine": "~2.8.6",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "~9.4.6",
    "codelyzer": "^4.3.0",
    "jasmine-core": "^3.1.0",
    "jasmine-spec-reporter": "^4.2.1",
    "karma": "^2.0.0",
    "karma-chrome-launcher": "^2.2.0",
    "karma-cli": "^1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "^1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "^5.3.0",
    "ts-node": "~5.0.1",
    "tslint": "^5.10.0",
    "typescript": "^2.8.3"
  }
}

what do we need to do?

When i downgrade to jasmine-core: "^2.9.0" the tests do run