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 }}
Repository navigation
Error running ng test while having an it call without the second parameter #4132
Chromium 55.0.2883 (Ubuntu 0.0.0) AppComponent encountered a declaration exception FAILED
TypeError: Cannot read property 'length' of undefined
at wrapTestInZone (webpack:///~/zone.js/dist/jasmine-patch.js:101:0 <- src/test.ts:51429:25)
at Env.jasmineEnv.(anonymous function) [as it] (webpack:///~/zone.js/dist/jasmine-patch.js:72:0 <- src/test.ts:51400:28)
at Suite.<anonymous> (webpack:///src/app/app.component.spec.ts:35:2 <- src/test.ts:67127:5)
at ZoneDelegate.invoke (webpack:///~/zone.js/dist/zone.js:242:0 <- src/test.ts:70686:26)
at Zone.run (webpack:///~/zone.js/dist/zone.js:113:0 <- src/test.ts:70557:43)
at Suite.<anonymous> (webpack:///~/zone.js/dist/jasmine-patch.js:89:0 <- src/test.ts:51417:29)
at Env.jasmineEnv.(anonymous function) [as describe] (webpack:///~/zone.js/dist/jasmine-patch.js:66:0 <- src/test.ts:51394:38)
at Object.<anonymous> (webpack:///src/app/app.component.spec.ts:6:0 <- src/test.ts:67102:1)
at __webpack_require__ (webpack:/webpack/bootstrap%205020e831b3ddab763f2e:19:0 <- src/test.ts:20:30)
at webpackContext (webpack:/src%20/.spec/.ts$:6:0 <- src/test.ts:51825:9)
at Array.map (native)
Mention any other details that might be useful.
I wanted to leave the test implementation for later, and followed this answer on stackoverflow.
It might not be an unwanted behavior, but I thought it would behave as a pending test and fail it as such, and the stacktrace barely indicates where the problem is.
Activity
filipesilva commentedon Jan 24, 2017
Can you open this issue on https://github.com/angular/zone.js/ instead please? It seems it's related to the jasmine patch used there.
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.