Skip to content

Running 'mojito test mojito path-to-mojit/mojit' returns an error. #526

zhouyaoji opened this Issue Sep 18, 2012 · 1 comment

2 participants


I created a new app w/ a mojit using Mojito v0.4.4 and then tried to use the test command to test the mojit: $ mojito test mojit path-to-mojit/mojit' Mojito threw an error similar to that specified in the closed issue 387: #387

Also see the following related issue: #525

The commands and the error message returned by Mojito are listed below:

$ mojito create app test_app
$ cd test_app
$ mojito create mojit test_mojit
$ mojito test mojit mojits/test_mojit

warn: (yui): NOT loaded: mojito-client
warn: (yui): NOT loaded: mojito-perf
warn: (yui): NOT loaded: mojito-perf

            throw (e || new Error(msg));
TypeError: Cannot read property 'documentElement' of null
    at Object.fn (/opt/local/lib/node_modules/mojito/node_modules/yui/dom-base/dom-base-min.js:7:50)
    at [object Object]._attach (/opt/local/lib/node_modules/mojito/node_modules/yui/yui-nodejs/yui-nodejs.js:701:33)

isao commented Nov 8, 2012

works now.

% mojito create app issue526
path.existsSync is now called `fs.existsSync`.
creating app type named 'issue526'
(using "default" archetype)
✔ app: issue526 created!
✔ mojito done.

% cd issue526/
%  mojito create mojit test_mojit
path.existsSync is now called `fs.existsSync`.
creating mojit type named 'test_mojit'
(using "default" archetype)
✔ mojit: test_mojit created!
✔ mojito done.

% mojito test mojit mojits/test_mojit
path.existsSync is now called `fs.existsSync`.
warn: (yui): NOT loaded: mojito-perf
warn: (yui): NOT loaded: mojito-perf

Test Results:

✔  passed test_mojit-tests :: test_mojit user tests :: test mojit
✔  passed test_mojitModelFoo-tests :: test_mojitModelFoo user tests :: test mojit model

Total tests: 2  ✔ Passed: 2   ⚑ Deferred: 0 ✖ Failed: 0   100% pass rate

% mojito version
path.existsSync is now called `fs.existsSync`.

Version of mojito is 0.4.8

✔ mojito done.
@isao isao closed this Nov 8, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.