document testing

[sberryman]

it looks like @rodfernandez is making some progress documenting in the development branch. his documentation has helped me quite a bit as it his examples seem easier to consume for me than the wiki (thanks @rodfernandez)

I can't seem to find any documentation on testing a lazo based app. what are you guys using internally? i'm assuming i should be looking at documentation on how to test a backbone based app right?

[jstrimpel]

There will be docs
https://github.com/walmartlabs/lazojs/tree/development/docs for the
following items within a couple weeks:

• views
• controllers
• models, collections, synchers and service proxy
• application singleton

A big thanks to @rodfernandez https://github.com/rodfernandez,
@michaeljacobdavis, and @subramgr. By the end of January all these docs
will make it to http://lazojs.org/ (under development).

For testing we were using grunt-castle
https://github.com/walmartlabs/grunt-castle, but are transitioning to
intern http://theintern.io/. There will be likely be a module that stubs
out the wiring for tests, but for now you can take a look at the lazo tests
themselves. There will also be a lazo mocks module, so you will not have to
create a bunch of mocks. We will probably have some functional testing in
intern examples. All of this will take time (over the next couple months),
but will eventually be housed under https://github.com/lazojs. We will
announce releases and notes twitter.

Jason

On Mon, Jan 12, 2015 at 9:32 AM, Shaun Berryman notifications@github.com
wrote:

it looks like @rodfernandez https://github.com/rodfernandez is making
some progress documenting in the development branch. his documentation has
helped me quite a bit as it his examples seem easier to consume for me than
the wiki (thanks @rodfernandez https://github.com/rodfernandez)

I can't seem to find any documentation on testing a lazo based app. what
are you guys using internally? i'm assuming i should be looking at
documentation on how to test a backbone based app right?

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