Testing?

[dgpt]

Should we do test driven development?

I say we do regression testing in a Behavior Driven style using Chai as the framework.

[parkm]

Yeah I guess it would be a good idea. I'm not sure on what we should write tests for though. I do like assert, it'd be helpful while debugging.

[dgpt]

Well, we'd make a testing folder with categories of tests for each module we make. Whenever we implement a new feature, we need to write a test to make sure it's working as intended.

This isn't /really/ necessary for this project, but it'd be REALLY good practice.

On Tue, Apr 29, 2014 at 9:47 PM, Parker Miller notifications@github.comwrote:

Yeah I guess it would be a good idea. I'm not sure on what we should write tests for though. I do like assert, it'd be helpful while debugging.

— Reply to this email directly or view it on GitHubhttps://github.com/despondentdonkey/bpm/issues/7#issuecomment-41757967 .

[parkm]

I suppose it won't hurt. You'll set up the framework for the project?

[dgpt]

Yeah, I can set up the framework. You should do some studying of testing though. There's a lot to it. Last month, I spent like three days just learning about testing.

[dgpt]

Do you wanna use Chai or QUnit? I'm gonna use Grunt as the test runner, btw.

[parkm]

I don't know. If they're pretty equal then just the most popular one I suppose.

[dgpt]

Okay, I prefer Chai, so we'll use Chai :)

On Thu, May 1, 2014 at 3:13 PM, Parker Miller notifications@github.comwrote:

I don't know. If they're pretty equal then just the most popular one I suppose.

— Reply to this email directly or view it on GitHubhttps://github.com/despondentdonkey/bpm/issues/7#issuecomment-41957618 .

[parkm]

Okay, sounds good.

[dgpt]

As decided on 5/10, we're dropping testing due to time constraints.