Closed semanticart closed 12 years ago
ah, i missed a param on the npm install. my fault.
I have the same issue. May I know what param did you miss in the npm install? Thanks
If i recall correctly it was
$ cd my_app
$ npm install .
But there's only a few npm commands so try the others if that doesn't cover it :)
I did npm install .
, of course.
I think my problem may be other.
I have hem 0.1.9, that uses an "unknown" version of Stich (I can not see the Stich version in the generated application.js
code).
I run hem server
, then I go to http://localhost:9294/test
and I see two errors:
GET http://localhost:9294/test/specs.js 404 (Not Found)
and
Uncaught ReferenceError: specs is not defined
It looks like this version of Stich does not get spec.modules
from the spec folder.
What should I do?
@marioizquierdo Same problem. I'm using Spine mobile if that makes a difference. Did you get anywhere in the end?
@amk221 I'm using Spine mobile as well. I ended up writing specs with plain Jasmine, in javascript. But this is driving to a less test-driven development, honestly the test coverage in my project is bad, but is a small project anyway.
On a fresh install of spine.app, I create a new app, cd into the directory and run
npm install
and thenhem server
When I visit http://localhost:9294/test the following line
throws the error
Uncaught ReferenceError: specs is not defined
The documentation around testing seems to be lacking, am I doing this wrong? I'd love to improve the docs if I can get it running.
Thanks