Meteor test driven development

I don't see how to do test driven development in meteor.

I don't see it mentioned anywhere in documentation or FAQ. I don't see any examples or anything like that.

I see that some packages are using Tinytest.

I would need response from developers, what is roadmap regarding this. Something along the lines of:

  • possible, no documentation, figure it out yourself
  • meteor is not built in a way that you can make testable apps
  • this is planned feature
  • etc

  • Update 3 : As of Meteor 1.3, meteor includes a testing guide with step-by-step instructions for unit, integration, acceptance, and load testing.

    Update 2 : As of November 9th, 2015, Velocity is no longer maintained. Xolv.io is focusing their efforts on Chimp, and the Meteor Development Group must choose an official testing framework.

    Update : Velocity is Meteor's official testing solution as of 0.8.1.


    Not much has been written about automated testing with Meteor at this time. I expect the Meteor community to evolve testing best-practices before establishing anything in the official documentation. After all, Meteor reached 0.5 this week, and things are still changing rapidly.

    The good news: you can use Node.js testing tools with Meteor .

    For my Meteor project, I run my unit tests with Mocha using Chai for assertions. If you don't need Chai's full feature set, I recommend using should.js instead. I only have unit tests at the moment, though you can write integration tests with Mocha as well.

    Be sure to place your tests in the "tests" folder so that Meteor does not attempt to execute your tests.

    Mocha supports CoffeeScript, my choice of scripting language for Meteor projects. Here's a sample Cakefile with tasks for running your Mocha tests. If you are using JS with Meteor, feel free to adapt the commands for a Makefile.

    Your Meteor models will need a slight bit of modification to expose themselves to Mocha, and this requires some knowledge of how Node.js works. Think of each Node.js file as being executed within its own scope. Meteor automatically exposes objects in different files to one another, but ordinary Node applications—like Mocha—do not do this. To make our models testable by Mocha, export each Meteor model with the following CoffeeScript pattern:

    # Export our class to Node.js when running
    # other modules, e.g. our Mocha tests
    #
    # Place this at the bottom of our Model.coffee
    # file after our Model class has been defined.
    exports.Model = Model unless Meteor?
    

    ...and at the top of your Mocha test, import the model you wish to test:

    # Need to use Coffeescript's destructuring to reference
    # the object bound in the returned scope
    # http://coffeescript.org/#destructuring
    {Model} = require '../path/to/model'
    

    With that, you can start writing and running unit tests with your Meteor project!


    Hi all checkout laika - the whole new testing framework for meteor http://arunoda.github.io/laika/

    You can test both the server and client at once.

  • See some laika example here
  • See here for features
  • See concept behind laika
  • See Github Repository
  • Disclaimer: I'm the author of Laika.


    I realize that this question is already answered, but I think this could use some more context, in the form of an additional answer providing said context.

    I've been doing some app development with meteor, as well as package development, both by implementing a package for meteor core, as well as for atmosphere.

    It sounds like your question might be actually a question in three parts:

  • How does one run the entire meteor test suite?
  • How does one write and run tests for individual smart packages?
  • How does one write and run tests for his own application?
  • And, it also sounds like there may be a bonus question in there somewhere: 4. How can one implement continuous integration for 1, 2, and 3?

    I have been talking and begun collaborating with Naomi Seyfer (@sixolet) on the meteor core team to help get definitive answers to all of these questions into the documentation.

    I had submitted an initial pull request addressing 1 and 2 to meteor core: https://github.com/meteor/meteor/pull/573.

    I had also recently answered this question: How do you run the meteor tests?

    I think that @Blackcoat has definitively answered 3, above.

    As for the bonus, 4, I would suggest using circleci.com at least to do continuous integration for your own apps. They currently support the use case that @Blackcoat had described. I have a project in which I've successfully gotten tests written in coffeescript to run unit tests with mocha, pretty much as @Blackcoat had described.

    For continuous integration on meteor core, and smart packages, Naomi Seyfer and I are chatting with the founder of circleci to see if we can get something awesome implemented in the near term.

    链接地址: http://www.djcxy.com/p/96630.html

    上一篇: JavaScript中的输出和原型是什么?

    下一篇: 流星测试驱动开发