Using sanjo:jasmine - publishFunctions is not defined on server

gabrielhpugliese · May 27, 2015, 12:47pm

expect(Meteor.publishFunctions).toBeDefined(); // fails

This fails for me on server side. I’ve read the source code of meteor-stubs and I thought it was stubbing that for me.
I’m probably doing something wrong but it’s not clear to me what it is.

Sanjo · May 27, 2015, 1:10pm

This is not a standard Meteor method. From which package is this?

gabrielhpugliese · May 27, 2015, 1:12pm

Maybe I’m getting things messy.
I mean this: https://github.com/meteor-velocity/meteor-stubs/blob/master/index.js#L211

I’m trying to test a publication, like this:

github.com

xolvio/Letterpress/blob/23e223b3d9d84abadde6a15ca515eae5b9cef460/tests/jasmine/server/unit/chaptersSpec.js#L3-L26


it("should return premium content to logged in users", function () {


  // SETUP
  var thisContext = {
    userId : true
  };


  var expectedCursor = 'chapter_cursor1';
  var _query = true, _modifiers = true;
  Chapters.find = function(query, modifiers) {
    _query = query;
    _modifiers = modifiers;
    return expectedCursor;
  };


  // EXECUTE
  var actualCursor = Meteor.publishFunctions['chapters'].apply(thisContext);


  // VERIFY
  expect(actualCursor).toBe(expectedCursor);

This file has been truncated. show original

Sanjo · May 27, 2015, 3:52pm

This should (only) work in server unit mode. If not I can have a look.

gabrielhpugliese · May 27, 2015, 4:14pm

Hmmm I haven’t done anything to differentiate unit and integrations tests. I think that’s why.
Here is the project: https://github.com/gabrielhpugliese/statuspage

I’ve just created that unit folder on the only package the project has. I suppose I had to do something more than that.

gabrielhpugliese · May 27, 2015, 4:18pm

Forgot to mention that I’m running with command VELOCITY_TEST_PACKAGES=1 meteor test-packages --driver-package velocity:html-reporter

Sanjo · May 28, 2015, 12:05am

Package testing only uses the Server Integration and Client Integration mode. So the stubs are not used.

I think you can test your publication with a client integration test by using Meteor.subscribe and then check the collection for the expected documents.

gabrielhpugliese · May 28, 2015, 2:08pm

Any possibility to patch the Meteor.publish function before the execution of code?

Sanjo · May 29, 2015, 5:28pm

No. But I think you can access your publish functions with Meteor.server.publish_handlers (Source: https://github.com/meteor/meteor/blob/master/packages/ddp/livedata_server.js#L1428)