Can you publish, please? npm is still at 0.0.1.

I removed a '2dsphere' index from my Mongoose schema, and ran 'load()' again, but it did not drop the index. I expected indexes to also be dropped and recreated as part of fixture resetting.

I was able to workaround the issue by manually dropping the index in question.

Other indexes besides 2dsphere indexes may be affected.

I might be wrong but it appears that if you use load('/path/to/directory') without specifying the db parameter, it does not work. After having a look at the code base, it seems that if you don't specify it, the db parameter is never set.

Mongoose gives you option to declare a connection:

var db = mongoose.createConnection('...');

load should be able to take an optional argument with this connection.

I have multiple database in a SINGLE NodeJS project.

example:

var conn      = mongoose.createConnection('mongodb://localhost/testA');
var conn2     = mongoose.createConnection('mongodb://localhost/testB');

// stored in 'testA' database
var ModelA    = conn.model('Model', new mongoose.Schema({
  title : { type : String, default : 'model in testA database' }
}));

// stored in 'testB' database
var ModelB    = conn2.model('Model', new mongoose.Schema({
  title : { type : String, default : 'model in testB database' }
}));

Then, I found this project get connection from mongoose.connection, but I don't set that. How to reslove?

I try to

fixtures.load(data, conn);

but failed.

hello,
I'm trying to load a file, and I get:

  TypeError: Cannot read property 'model' of undefined

I'm using pow-mongoose-fixtures 0.3.0.

It turns out that on line 18:

 if (typeof db === 'function') {
    callback = db;
    db = mongoose.connection;
}

this block is never called if I don't specified other that 1 parameters to load method.

typeof db in my case is always "undefined".

Is that because I'm using typescript?

I have a model that performs a check in the "pre-save" hook, and calls back with an error if the check fails. That error never makes it out of the "insertObject" code, but the objects aren't getting successfully inserted so the insertObject callback is never called and the code reliably times out in my tests.

Ref: https://mongoosejs.com/docs/deprecations.html

I was experiencing an issue so I started by reading the code in this repository. It seemed like everything should work.

It turns out that I was using the mongoose-fixtures module when I should have been using the pow-mongoose-fixtures module.

Please deprecate the old module in npm. If possible, point the old module to the new module (not sure if this is doable).

Hi,

On line 30 of mongoose_fixtures.js there's OS specific code:

    //Get the absolute dir path if a relative path was given
    if (data.substr(0, 1) !== '/') {

I can't really use full, valid paths in Windows since the drive letter would be duplicated (e.g. c:\c:\test\fixture.js).

I wanted to send a pull request, but I couldn't run the existing tests, as npm install tries to clone "git://github.com/OpenifyIt/commons.git" which doesn't seem to exist (am I missing something in the setup, or is it outdated?).

Thanks.

Hello,

I did a fork and implement a plan to use the glob function (node-glob), which lets you filter with a regular expression the files / folders

But the tests are not passing here in my environment, I am using Mac OS X 10.8.3, node js v0.10.3, mongodb 2.2.0

So I could test, I changed the function "before" test, looked like this:

    before(function(done){
        mongoose.connect(process.env.MONGODB_URL);
        require('./models/country.coffee');
        done();

        // this.mongooseInitializer = new MongooseInitializer(process.env.MONGODB_URL, path.join(__dirname, './models'));

        // var functions = [
        //     this.mongooseInitializer.openConnection,
        //     this.mongooseInitializer.loadModels
        // ];
        // async.series(functions, done);
    });

It seems that the problem here in my environment is that the flow asynchronous this a problem with async.series, but I have not found

thank you
hugs

Hi,

I have a simple test.coffee file:

fixtures    = require('pow-mongoose-fixtures')

API       = new (require(__dirname + '/../server'))
api       = supertest(API.app)

fixtures.load(__dirname + '/fixtures/users.js')

And my users.coffee:

exports.Users =
    user1: {
        firstName: 'John'
        lastName: 'Doe'
    }

The server is running my server (no kidding). Now, I don't get why the fixtures are not loading. I don't have any error but it doesn't clear the collection nor populate it.

Any idea? An example implementation?

Can you push latest github version to NPM?

When there is a capped collection in the project, it is impossible to call remove() on it (MongoError, only drop() works).
But mongoose_fixtures.js does exactly that.
So everything dies.

I suggest to add a clause for isCapped() -> true which would clone -> drop -> rename collection as a safe way of cleaning.

Is it possible to pass the newly inserted fixtures to your callback, so you don't have to query your database in your tests? I'm thinking something along the lines of:

// fixtures/user.js
module.exports.User = {
  admin: { email:'[email protected]' , ... },
  user_1: { email:'[email protected]', ... },
  user_2: { email:'[email protected]', ... }
}

// tests.js
setup(function(done){
  fixtures.load('./users.js', function(users){
    self.users = users;
    done(); 
  })
});

test("Example Test", function(done){
  app.login(self.users.user_1);
  // test something here
  done();
});

If this is something you're interested in, I'd be happy to contribute a patch. Otherwise I'll probably just wrap your fixture module in my own module to accomplish the same thing in my project.

The repo of openifyit-commons (which is required in package.json ) does not exist anymore. So, this part of code does not work.

On Windows, path given to Fixtures.load() gets resolved to C:\C:\... wich leads to Error: ENOENT (it can not be found).