Do you have any tutorial about exposing the object to be tested and referring a dependency
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- documentation, testing
Research direction
Start with the testrunner configuration described in the issue, especially the code setting, and determine how application objects and dependencies are loaded for tests. Check the existing usage documentation and examples for a supported Sinon integration path; done means a newcomer can follow a documented example to access application code and use Sinon in a test.
Written by the indexing model from the issue text.
Description
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:
{
code: "path/to/mycode",
}
but how can I get access to my vars, objects and dear sinon.
- Dominant language
- JavaScript
- Stars
- 171
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from qunitjs/node-qunit
-
support
Difficulty 5/5 Over a week Newbie friendliness 30/100
qunitjs/node-qunit#142 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
qunitjs/node-qunit#140 ·
-
documentation help welcome problem
Difficulty 1/5 Under an hour Newbie friendliness 55/100
qunitjs/node-qunit#135 ·
-
problem
Difficulty 3/5 1-2 days Newbie friendliness 42/100
qunitjs/node-qunit#131 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
qunitjs/node-qunit#128 · 3 comments ·
All issues in qunitjs/node-qunit
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vadimdemedes/ink#1029 ·
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·