Testing Framework Workflow Integration

[kgrgreer]

Tests should be verified as part of the check-in process an/or when files are updated.

[bshepherdson]

Sketching out my plan:

• Set up a Node-based, console output test runner, ideally one that can enumerate every unit test in the framework.
• Add a grunt task that will make running these tests once, or watching and running repeatedly, easy.
• Probably add a precommit (prepush?) hook that ensures the tests stay green?
• Travis CI?

[kgrgreer]

First three look good to me.

On 7 May 2014 14:16, Braden Shepherdson notifications@github.com wrote:

Sketching out my plan:

• Set up a Node-based, console output test runner, ideally one that can enumerate every unit test in the framework.
• Add a grunt task that will make running these tests once, or watching and running repeatedly, easy.
• Probably add a precommit (prepush?) hook that ensures the tests stay green?
• Travis http://travis-ci.org CI?

— Reply to this email directly or view it on GitHubhttps://github.com/foam-framework/foam/issues/234#issuecomment-42463096 .

[bshepherdson]

Alas it didn't go much farther than the early stages of the above plan.

We no longer use Grunt, rather our own Node-powered tools. Tests can be run at the command line or in your browser for any model. We don't currently comb the framework for tests.

• [x] Console test runner
• [ ] Update the pre-commit hook to use the new tools.
• [ ] Get the set of tests run by that hook passing.
• [ ] Get everyone using the hook on their various machines.
• [ ] Set up continuous integration somewhere; probably Travis.
• [ ] Comb the codebase for tests on models and run them all.
• [ ] Add enabled: false support to the UnitTest model to allow deletion without removing or commenting out a test
  • [ ] Display the number and names of disabled tests nicely in the test runner.