Skip to content
This repository was archived by the owner on Feb 26, 2024. It is now read-only.

Testing: 'descripe' is not defined (with karma and protractor) #301

Closed
TBoonX opened this issue Oct 21, 2015 · 1 comment
Closed

Testing: 'descripe' is not defined (with karma and protractor) #301

TBoonX opened this issue Oct 21, 2015 · 1 comment

Comments

@TBoonX
Copy link

TBoonX commented Oct 21, 2015

With protractor or karma 'descripe' of jasmine is not defined.
I cleaned all of bower, npm and node.js and reinstalled it. I just used this project with 'npm install'.
If I call protractor directly, the same error occurs.
jasmine is installed in the directory node_modules.
I tried to include jasmine-core.js in protractor.conf.js.
protractor uses the correct config file.

Please help me with this. I really want to write tests!

npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'c:\Program Files\nodejs\node.exe',
1 verbose cli 'c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'protractor' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'preprotractor', 'protractor', 'postprotractor' ]
5 info preprotractor [email protected]
6 verbose unsafe-perm in lifecycle true
7 info protractor [email protected]
8 verbose unsafe-perm in lifecycle true
9 info [email protected] Failed to exec protractor script
10 verbose stack Error: [email protected] protractor: protractor e2e-tests/protractor.conf.js
10 verbose stack Exit status 1
10 verbose stack at EventEmitter. (c:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:214:16)
10 verbose stack at emitTwo (events.js:87:13)
10 verbose stack at EventEmitter.emit (events.js:172:7)
10 verbose stack at ChildProcess. (c:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
10 verbose stack at emitTwo (events.js:87:13)
10 verbose stack at ChildProcess.emit (events.js:172:7)
10 verbose stack at maybeClose (internal/child_process.js:818:16)
10 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
11 verbose pkgid [email protected]
12 verbose cwd c:\Entwicklung\AgriConnect\Test\angularseed
13 error Windows_NT 6.1.7601
14 error argv "c:\Program Files\nodejs\node.exe" "c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "protractor"
15 error node v4.2.1
16 error npm v2.14.7
17 error code ELIFECYCLE
18 error [email protected] protractor: protractor e2e-tests/protractor.conf.js
18 error Exit status 1
19 error Failed at the [email protected] protractor script 'protractor e2e-tests/protractor.conf.js'.
19 error This is most likely a problem with the angular-seed package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error protractor e2e-tests/protractor.conf.js
19 error You can get their info via:
19 error npm owner ls angular-seed
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]

Console output:
$ npm run protractor

[email protected] preprotractor c:\Entwicklung\AgriConnect\Test\angularseed
npm run update-webdriver
[email protected] preupdate-webdriver c:\Entwicklung\AgriConnect\Test\angular
seed
npm install
[email protected] postinstall c:\Blub\angularseed
bower install
[email protected] update-webdriver c:\Blub\angularsee
d
webdriver-manager update
selenium standalone is up to date.
chromedriver is up to date.
[email protected] protractor c:\Blub\angularseed
protractor e2e-tests/protractor.conf.js
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://192.168.99.101:61730/wd/hub
F

Failures:

  1. Exception loading: c:\Blub\angularseed\e2e-tests\te
    stCtrlTasklist.js Error
    Message:
    ReferenceError: descripe is not defined
    Stacktrace:
    ReferenceError: descripe is not defined
    at Object. (c:\Blub\angularseed\e2e-tests
    \testCtrlTasklist.js:1:63)
    at require (module.js:385:17)
    at Object.exports.executeSpecs (c:\Blub\angularseed
    node_modules\protractor\node_modules\minijasminenode\lib\index.js:130:7)
    at c:\Blub\angularseed\node_modules\protractor\lib\f
    rameworks\jasmine.js:88:14
    at Function.promise (c:\Blub\angularseed\node_module
    s\protractor\node_modules\q\q.js:650:9)

Finished in 0.017 seconds
1 test, 1 assertion, 1 failure

Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 failed 1 test(s)
[launcher] overall: 1 failed spec(s)
[launcher] Process exited with error code 1

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\Program Files\nodejs\node.exe" "c:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "run" "protractor"
npm ERR! node v4.2.1
npm ERR! npm v2.14.7
npm ERR! code ELIFECYCLE
npm ERR! [email protected] protractor: protractor e2e-tests/protractor.conf.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] protractor script 'protractor e2e-test
s/protractor.conf.js'.
npm ERR! This is most likely a problem with the angular-seed package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! protractor e2e-tests/protractor.conf.js
npm ERR! You can get their info via:
npm ERR! npm owner ls angular-seed
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! c:\Blub\angularseed\npm-debug.log

@TBoonX TBoonX closed this as completed Oct 22, 2015
@TBoonX
Copy link
Author

TBoonX commented Oct 22, 2015

I misspelled the method ...
Sorry for distraction.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant