linkedin / dustjs

Asynchronous Javascript templating for the browser and server
http://dustjs.com
MIT License
2.91k stars 478 forks source link

No result when running tests on server #81

Closed seriousManual closed 12 years ago

seriousManual commented 12 years ago

When I'm running the serverside jasmine test-suite I'm always getting this result:

[zap@meg server]$ node specRunner.js
undefined

Finished in 0.006 seconds
0 tests, 0 assertions, 0 failures

This happens on my Windows7 machine as well as on every other Linux Server I ran it.

Am I missing a dependency?

The client side tests are running well.

vybs commented 12 years ago

@zaphod1984 https://github.com/linkedin/dustjs/blob/master/test/README.md

any case you missed the above steps?

jairodemorais commented 12 years ago

try running the test with the make command. Execute "make jasmine" in the dust root folder.

seriousManual commented 12 years ago

hi, thanks for your reply, I did exactly as specified. for clearification:


zaphod@CARTMAN:~/node/node_modules/dustjs-linkedin$ sudo npm install -g jasmine-node
npm http GET https://registry.npmjs.org/jasmine-node
npm http 304 https://registry.npmjs.org/jasmine-node
npm http GET https://registry.npmjs.org/coffee-script
npm http GET https://registry.npmjs.org/jasmine-reporters
npm http GET https://registry.npmjs.org/requirejs
npm http GET https://registry.npmjs.org/walkdir
npm http GET https://registry.npmjs.org/underscore
npm http 304 https://registry.npmjs.org/jasmine-reporters
npm http 304 https://registry.npmjs.org/coffee-script
npm http 304 https://registry.npmjs.org/requirejs
npm http 304 https://registry.npmjs.org/walkdir
npm http 304 https://registry.npmjs.org/underscore
/usr/local/bin/jasmine-node -> /usr/local/lib/node_modules/jasmine-node/bin/jasmine-node
jasmine-node@1.0.26 /usr/local/lib/node_modules/jasmine-node
âââ walkdir@0.0.4
âââ underscore@1.3.3
âââ coffee-script@1.3.3
âââ requirejs@2.0.2
âââ jasmine-reporters@0.2.1
zaphod@CARTMAN:~/node/node_modules/dustjs-linkedin$ make jasmine
node test/jasmine-test/server/specRunner.js
undefined

Finished in 0.007 seconds
0 tests, 0 assertions, 0 failures

zaphod@CARTMAN:~/node/node_modules/dustjs-linkedin$ node test/jasmine-test/server/specRunner.js
undefined

Finished in 0.008 seconds
0 tests, 0 assertions, 0 failures

zaphod@CARTMAN:~/node/node_modules/dustjs-linkedin$
jairodemorais commented 12 years ago

@zaphod1984 hi man! as I can see you are using the server dust version right? well first of all take a look if you have the test file, it is called examples.js and it is located in "test/jasmine-test/spec/", this file has a json file with all the dust test. Anyway I have released the version 1.0.0 for npm, try updating your linkedin-dustjs package.

seriousManual commented 12 years ago

I was just about to comment on this issue when I realized that it's closed...

@jairodemorais every file is present as stated before the tests are running fine in the browser. updating didn't help either.

vybs commented 12 years ago

i tried to install node 0.6 from clean install the node jasmine-node and then ran all the tests.

it worked all fine. So we are missing something from your environement

seriousManual commented 12 years ago

I've tested on three different machines, with three different operating systems and node versions:

Fedora release 16 (Verne), node 0.7.12 Debian GNU/Linux, node 0.7.12 Win7 x64, node 0.8.2

Is 0.6 mandatory for the tests? What else could it be?

jairodemorais commented 12 years ago

@zaphod1984 any news about this? because I could not reproduce it, I have installed node 0.8 and everything is working great for me.

seriousManual commented 12 years ago

still not running...

jairodemorais commented 12 years ago

@zaphod1984

Please:

I want to reproduce the same scenario that you have.

seriousManual commented 12 years ago

@jairodemorais thanks for the effort!

zaphod@CARTMAN:~/node/node_modules/dustjs-linkedin$ npm list
dustjs-linkedin@0.6.0 /home/zaphod/node/node_modules/dustjs-linkedin
ââ⬠jasmine-node@1.0.22
   âââ coffee-script@1.2.0
  ââ⬠findit@0.1.2
  â ââ⬠seq@0.3.5
  â   ââ⬠chainsaw@0.0.9
  â   â âââ traverse@0.3.9
  â   ââ⬠hashish@0.0.4
  â     âââ traverse@0.6.0
  âââ jasmine-reporters@0.2.1
  âââ requirejs@1.0.7
  âââ underscore@1.3.1

zaphod@CARTMAN:~/node/node_modules/dustjs-linkedin$ node -v
v0.8.2
jairodemorais commented 12 years ago

@zaphod1984 hi man! I think that it is a problem with the jasmine-node package, take a look https://github.com/mhevery/jasmine-node/issues/118, anyway I am still researching.

:)

seriousManual commented 12 years ago

Thanks man! The issues mentioned in your linked issue matches exactly the behaviour that I'm experiencing!