-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do you have any tutorial about exposing the object to be tested and referring a dependency #90
Comments
There is a deps option for this. See api documentation or shell script help. |
I'm also having trouble figuring out how to use my objects and vars in my tests. If I have a runner set up like this:
In What is the solution? I added my code to |
exports are merged with global when namespace is not defined. So by default you can access CLI.bla from global.bla or just bla. If you add namespace (see documentation) you will get CLI attached to global using this namespace, f.e. namespace: 'CLI' .... global.CLI === CLI Its designed to work similar to the browser. Please submit a pull request for the documentation if I could help you. |
I was able to fix this by adding a |
Can you please change the readme file so that you would not stumble over this issue a second time? |
I just guess you made a great lib of qunit. But cannot find any information about how to referring/requiring/my code to be tested and I also need to use sinon to mock something how can I include sinonjs in my testing?
I mean I know the testrunner has some thing like:
but how can I get access to my vars, objects and dear sinon.
The text was updated successfully, but these errors were encountered: