Incomplete tests/setups/teardowns with RequireJS
- Langage dominant
- JavaScript
- Étoiles
- 1.9k
- Forks
- 359
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Here is my test (using grunt-contrib-nodeunit):
```
var requirejs = require('requirejs');
exports.test = function(test){
test.expect(1);
requirejs(['dist/test-hts'],function(obj){
test.ok(true, 'hello');
test.done();
});
};
```
For some reason, this doesn't work! It appears as though RequireJS doesn't play nice with node unit. I've been trying to get testing working for the better part of 3 days with no luck so far, even on the most simple of tests like above!
This happens when I run with vanilla nodeunit from the command line:
```
test.js
FAILURES: Undone tests (or their setups/teardowns):
- test
To fix this, make sure all tests call test.done()
```
If I move the `.done()` to the outside of the callback, it just skips the test all together and says that it expected 1 assertion but found none.
I have also tried it this way:
```
var requirejs = require('requirejs');
requirejs.config({
nodeRequire: require,
baseUrl: __dirname
});
requirejs(['../dist/test-hts'],function(obj){
console.log('loaded...');
exports.test = function(test){
test.expect(1);
test.ok(true, 'hello');
test.done();
};
});
```
It results in:
```
OK: 0 assertions (41ms)
```
Also, if I run this same file using node rather than nodeunit (just to check execution), I get the following output:
```
loaded...
```
So I know that the module is loading properly, just not with nodeunit!
Any help here would be great. I don't understand why nodeunit wouldn't work with such a well-known AMD tool like RequireJS. Thanks!
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par reproduire le test.js fourni avec vanilla nodeunit et la configuration de grunt-contrib-nodeunit. Suivez la manière dont nodeunit découvre le test et gère test.done() pendant que le callback RequireJS charge dist/test-hts. C’est terminé lorsque l’exemple s’exécute sans erreur liée à un test non terminé et enregistre l’assertion attendue.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- testing-qa
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100