Hi All, after a long time being a meteor user, I’ve decided it’s time to give something back, so I created a package for testing meteor packages using describe, context, it blocks with Tinytest underneath.
… long story short: smithy:describe …
I’ve struggled with tests for a long time, but lately I’ve been moving towards a “packages only” app, and writing tests using the great Tinytest package created by MDG. Meteor itself is tested with it, so I assumed it is the safest bet.
While I was able to structure my tests using tinytest only, I missed how I was able to define my test suite using before, after, beforeEach and afterEach calls and after seeing a package that was trying address this same problem (peterellisjones:describe), I decided to give it a try.
So I released the package named: smithy:describe. It’s the very first version, and it only wraps
Tinytest.add, although it may not be so hard to add
Tinytest.addAsync support following peterellisjones:describe code. I had to implement
it so they all add a new test, this is what makes the whole suite run in the expected order after a change (and not just the
it part as I experienced on early commits).
I hope to hear some comments, suggestions and feedback and what I hope the most, is that this is helpful for someone else.
Thanks to all the community and MDG.