hello Meteor friends,
I’m starting to play around with full-app testing lately, but i have a big app with a TON of collections and schemas. writing a separate factory schema for each collection feels like I’m repeating myself when I don’t necessarily have to - not to mention issues arising if the two don’t match, etc.
my initial thought is that you could possibly add a fake() method to collections. i.e use the SimpleSchema as the Factory.define(), and then Collection.fake() to generate the documents. the reasoning would be that your schemas and test collection definitions are coming from the same place?
does this line of reasoning make sense, or would it be redundant to implement something like this?