Tests aren't running when I invoke `meteor --once` (on windows)

[zacharynevin]

Hello,

I am on a windows machine, so the command RUN_TESTS=1 meteor --once doesn't work for me - I have to set my environment variable to RUN_TESTS=1 from the control panel, which I've done.

When I go into the root meteor directory and run meteor --once, nothing happens. It shows some logs about Selecting package versions and all that, as if it is starting a Meteor app.

My app is structured like this:

/my-app
  Readme.md
  /src
    /server
      /publications
      /methods
        methodOne.js
        methodOne-spec.js
    /client

I have put my example spec file into my server directory (see above). methodOne-spec.js is structured in the following way:

T.suite(function() {
    describe('example method', function() {
        context('test case', function() {
            it('should return true', function() {
                var t = true;
                t.should.be.ok()
            })
        });
    });
});

P.S. love the idea of this package. I was getting really tired of the overhead in Velocity.

[zacharynevin]

False alarm! I got it to work by removing all the velocity packages!

However, I have to manually start MongoDB on port 3001 in order for it to work.

[zacharynevin]

I also had to remove the --once parameter in order for it to run (so I had to run two MongoDB instances - one on port 27017 and one on port 3001)

[taromero]

Hi @zacharynevin, glad you liked the idea of the package! And also that you got it working on Windows (since I couldn't test it myself). I have some observations that might help:

1. What version of latte are you using? Some versions ago I removed the need (and actually the API method) to call T.suite, so you could remove that line on your example.
2. Regarding the Mongo issue, on what port is your app's DB running? are you using the default Mongo DB that Meteor boots on a new project? or do you connect to a different DB? In the first case, you should not have any problem since your app should start a Mongo instance on port 3001 (assuming you run the app on port 3000). In the second case, you have to set the db connection for latte to point to run running server (27017). You can do this by declaring T.testingDbUrl = mongodb://127.0.0.1:27017/meteor_latte somewhere in your application that runs before latte tests (basically anywhere that runs before Meteor.startup).

Please let me know the latte version that you are using, and if 2 fixed the DB problem.

[zacharynevin]

That worked. However, I notice that errors don't get displayed when RUN_TESTS is on. As a result, if there is a syntax error or other issue with the tests (e.g. Undefined variable), I don't know unless I pour through the code.

On 9 Aug, 2015, at 8:13 am, taromero notifications@github.com wrote:

Hi @zacharynevin, glad you liked the idea of the package! And also that you got it working on Windows (since I couldn't test it myself). I have some observations that might help:

What version of latte are you using? Some versions ago I removed the need (and actually the API method) to call T.suite, so you could remove that line on your example.
Regarding the Mongo issue, on what port is your app's DB running? are you using the default Mongo DB that Meteor boots on a new project? or do you connect to a different DB? In the first case, you should not have any problem since your app should start a Mongo instance on port 3001 (assuming you run the app on port 3000). In the second case, you have to set the db connection for latte to point to run running server (27017). You can do this by declaring T.testingDbUrl = mongodb://127.0.0.1:27017/meteor_latte somewhere in your application that runs before latte tests (basically anywhere that runs before Meteor.startup).
Please let me know the latte version that you are using, and if 2 fixed the DB problem.

—
Reply to this email directly or view it on GitHub.

[taromero]

Mm, that's completely unexpected to me, since latte doesn't wrap the application in any way (and I remember seeing undef errors while working with latte, if that's of any value). I can't actually try it myself right now since I'm on vacation (I only have access to my gf's Chromebook).

I tried to quickly come up with an example using Meteor Pad without success. I'll try it again with more time later.