摩卡testing花费太长的时间来执行

所以我正在一个express.js应用程序，我有一个mongoose模型用户。 我写了一个testing文件（使用Mocha）来testingsave（）函数，但是我所有的testing都花费很长时间来执行并最终超时。

这是我得到的错误：

Testing - Server - User - Model Testing save() 1) should be able to save without problems 2) should fail to save an exisitng user again 3) should should an error when try to save with empty email 4) should give an error when try to save with empty password 5) "after all" hook 0 passing (8s) 5 failing 1) Testing - Server - User - Model Testing save() should be able to save without problems: Error: timeout of 2000ms exceeded at null.<anonymous> (/usr/local/lib/node_modules/mocha/lib/runnable.js:159:19) at Timer.listOnTimeout [as ontimeout] (timers.js:112:15) 2) Testing - Server - User - Model Testing save() should fail to save an exisitng user again: Error: timeout of 2000ms exceeded at null.<anonymous> (/usr/local/lib/node_modules/mocha/lib/runnable.js:159:19) at Timer.listOnTimeout [as ontimeout] (timers.js:112:15) 3) Testing - Server - User - Model Testing save() should should an error when try to save with empty email: Error: timeout of 2000ms exceeded at null.<anonymous> (/usr/local/lib/node_modules/mocha/lib/runnable.js:159:19) at Timer.listOnTimeout [as ontimeout] (timers.js:112:15) 4) Testing - Server - User - Model Testing save() should give an error when try to save with empty password: Uncaught AssertionError: expected null to exist at Promise.<anonymous> (/Users/Mukul/PersonalProjects/ResourceBucket/test/models/user.server.model.test.js:69:12) at Promise.<anonymous> (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8) at Promise.emit (events.js:98:17) at Promise.emit (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/mpromise/lib/promise.js:84:38) at Promise.fulfill (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/mpromise/lib/promise.js:97:20) at handleSave (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/lib/model.js:133:13) at /Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/lib/utils.js:408:16 at model.save (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/lib/model.js:222:7) at model._done (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/hooks/hooks.js:59:24) at _next (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/hooks/hooks.js:52:28) at fnWrapper (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/hooks/hooks.js:159:8) at model.<anonymous> (/Users/Mukul/PersonalProjects/ResourceBucket/models/user.js:22:46) at _next (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/hooks/hooks.js:50:30) at fnWrapper (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/node_modules/hooks/hooks.js:159:8) at complete (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/lib/document.js:992:5) at /Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/lib/document.js:983:20 at ObjectId.SchemaType.doValidate (/Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/lib/schematype.js:603:22) at /Users/Mukul/PersonalProjects/ResourceBucket/node_modules/mongoose/lib/document.js:974:9 at process._tickCallback (node.js:442:13) 5) Testing - Server - User - Model "after all" hook: Error: timeout of 2000ms exceeded at null.<anonymous> (/usr/local/lib/node_modules/mocha/lib/runnable.js:159:19) at Timer.listOnTimeout [as ontimeout] (timers.js:112:15) 

这是我的testing文件：

 // Module dependencies var should = require("should"); var mongoose = require("mongoose"); var config = require('../../config/config'); var nodemailer = require('nodemailer'); var bcrypt = require('bcryptjs'); // Get User model var User = require('../../models/user')(mongoose, config, bcrypt, nodemailer).User; // Define global test variables var user; var user2; // Unit tests describe('Testing - Server - User - Model', function(){ // Since its before - it happens once ONCE before ALL the tests before(function(done){ // Since we're using the global variables don't use var in front of them user = new User({ email: '[e-mail]', password: 'a' }); // Another user with same details as the first user cos // For a test case, where we try to insert 2 records with same details (should fail as exprected) user2 = new User({ email: '[e-mail]', password: 'a' }); done(); }); // Testing function #1 - save() describe('Testing save()', function(){ // Test case #1 - save normally it('should be able to save without problems', function(done){ try { user.save(done); } catch (x) { done(x); } }); // Test case #2 - should fail to save an exisitng user again it('should fail to save an exisitng user again', function(done){ user.save(function(){ user2.save(function(err){ should.exist(err); done(); }); }); }) // Test case #3 - should give an error when try to save with empty email it('should should an error when try to save with empty email', function(done){ user.email = ''; return user.save(function(err){ should.exist(err); done(); }); }); // Test case #4 - should give an error when try to save with empty password it('should give an error when try to save with empty password', function(done){ return user.save(function(err){ should.exist(err); done(); }); }); }); after(function(done){ User.remove().exec(done); }); }); 

这里是我的用户模型文件：

 module.exports = function(mongoose, config, bcrypt, nodemailer){ // User schema var userSchema = new mongoose.Schema({ email: { type: String, unique: true, lowercase: true }, password: { type: String, select: false } }); // Makes sure that our passwords are always hashed before saving to the database // Refer to sessionBuddy's resources for more info on this userSchema.pre('save', function(next) { var user = this; // Only hash the password if its modified or new if (!user.isModified('password')) return next(); // Generate salt bcrypt.genSalt(config.SALT_WORK_FACTOR, function(err, salt) { if (err) return next(err); // hash the password along with the salt bcrypt.hash(user.password, salt, function(err, hash) { if (err) return next(err); // overwrite the cleartext password with the hashed one user.password = hash; next(); }); }); }); // Password verification for cleartext and hashed passwords userSchema.methods.comparePassword = function(password, done) { bcrypt.compare(password, this.password, function(err, isMatch) { done(err, isMatch); }); }; var User = mongoose.model('User', userSchema); return{ User : User } } 

我也尝试了这个线程的承诺的try / catch方式： 在调用asynchronous函数的摩卡testing中如何避免超时错误：超过2000ms的超时。 但是那也行不通。

任何帮助表示赞赏！ 谢谢

编辑：正如在评论中build议我没有连接到testing文件中的数据库。 编辑2：获取最后2testing现在的错误 – “未捕获AssertionError：预期空存在”编辑3：其实我的模式是保存“电子邮件”和“密码”空，因为我没有设置必填字段为真，更新我的模式后，它的作品。

Answer 1

正如在评论中指出的，你并没有真正连接到MongoDB数据库。 所有的请求都会被Mongoose排队，并且在连接到数据库之前永远不会被执行（从而在testing中产生超时）。

编辑至于你的第二个问题，你期望错误存在，当它实际上不产生任何错误。 这条线没有通过testing：

 should.exist(err); 

你应该检查你的模型。 在你的第三个testing案例中，你需要一个用户有一个电子邮件，但你的模型不强制执行。 同样的事情的密码。 另外，你在testing中没有把密码设为空。