Post v2 testing strategy

[samccone]

As always we should require unit tests for each feature added.
We should also require unit tests proving bugs when we run into them.

As part of the travis build we should have a suite of integration tests.

• testing a real app with the latest build
  https://github.com/Puppets/dill.js-getting-started
• testing convoluted and or complex operations
  • rendering deeply nested trees
  • complex behavior interactions

---

Thoughts?

[jasonLaster]

That'd be great. Sometimes a sample app or two is the best way to get these "complex" interactions. Like it's hard to imagine what they would be until they're actually used.

So, my crazy idea would be to see if some people would be willing to "contriubte" their app & integration tests for testing. Like most of our releases should be "non-breaking" so we should be able to run their suite of tests and have everything work...

[samccone]

Closing as much progress has been made on this on a lot of different fronts.
We have integration tests, they just dont run as part of the repo.