it("can add to and read from Meteor collections", function () {
expect(Meteor.instantiationCounts.url).toBe(1);
Url.insert({test : 'abc'});
console.log(Url.find({}).fetch());
});
});
/app/models/url:
Url = new Meteor.Collection("url");
I'm sure I'm missing something obvious here but that console.log is outputting undefined.
Is there any way that RTD can be used to test Collection CRUD functionality?
Note When I console.log Url I get an empty object. I'm guessing something within Core Meteor may not be available from within an RTD unit testing context?
Take the below for example:
/tests/model/url.js:
/app/models/url:
I'm sure I'm missing something obvious here but that console.log is outputting undefined.
Is there any way that RTD can be used to test Collection CRUD functionality?
Note When I console.log Url I get an empty object. I'm guessing something within Core Meteor may not be available from within an RTD unit testing context?