CODEWITHSUNDEEP
unit-testingmeteormocha.js
Sprintup
Sprintup

Reputation: 93

How to make a unit test in meteor that adds a document to a collection? Mocking userId

Thank you for your help-

I'd like to know if my app successfully adds a document to the database using a unit test in Meteor. I'm using practicalmeteor:mocha and chai. The issue I'm running into is that I don't know how to mock a this.userId, it keeps telling me I'm not logged in. 

it('inserts the draft agenda document into the collection', function() {
      // TODO: mock document to insert into collection		  	
      // TODO: mock userId and Agenda.insert		  		
      this.userId = "Not an empty string";
      console.log("before spec, changing this.userId: " + this.userId) //is "Not an empty string"

      Meteor.call('createAgenda', mockAgenda, function(res) {
          console.log("callback with response: " + res); //You're not logged-in. [not-logged-in]		    		
          console.log("this.userId: " + this.userId) //is undefined
        }
}

Thank you for your help, any code examples would be great.

Upvotes: 0

Views: 318

Answers (1)

Mysteric
Mysteric

Reputation: 106

Remarks

I wanted to post a comment but do not have enough reputation. So here are some remarks. Since you are testing on the server, you can call a Meteor method without a callback. This will result in a synchronous execution and simplify your test. Otherwise you will have to let the test know it is finished by calling the done function in your callback, see mocha docs.

Using mdg:validated-method

You can call a valited method and provide the context in which they execute using the _execute function. Below is an example taken from the todos sample project. For more examples you can take a look at their Lists and Todos tests.

it('makes a list private and updates the todos', function() {
  // Check initial state is public
  assert.isFalse(Lists.findOne(listId).isPrivate());

  // Set up method arguments and context
  const methodInvocation = {
    userId
  };
  const args = {
    listId
  };

  // Making the list private adds userId to the todo
  makePrivate._execute(methodInvocation, args);
  assertListAndTodoArePrivate();

  // Making the list public removes it
  makePublic._execute(methodInvocation, args);
  assert.isUndefined(Todos.findOne(todoId).userId);
  assert.isTrue(Todos.findOne(todoId).editableBy(userId));
});

Using standard methods

Another possiblity would be to bind the standard call function to the correct context. Note that this is just a thought and not tested.

var methodInvocation = {
  userId: "some user id"
};

Meteor.call.bind(methodInvocation)('createAgenda', mockAgenda);

Upvotes: 3

Related Questions