TDD choices

[1000i100]

i'm thinking about TDD file structure, test execution and test build process.
I think tests shoold be processed by docpad to be run in dev environnement (if test are written in coffeescript, they will be converted in js by docpad then put in a web browsable folder for live use in dev environnement. (so it's possible to test in as many browser as we want)
when running grunt to build the prod environnement, it should run all tests in the build process (thanks to grunt-cafe-mocha and phantomjs) and log result in a file using html-cov reporter (i will probably use extra json-cov reporter for test-metrics historic generation as quality tracker like SonarQube do but in a lighter way).

So to reach this goal what's the most logical position for test files ?

• test folder in project root ? (good visibility for developers but extra rules need to use it in docpad)
• test folder in src folder ? (probably easier to use in dev environment, but harder to not let them pollute prod build with test files and libs).

inside test folder :

• we can directly put test files
• we can have a spec folder to put test files, a lib folder for test libs and a live runner file directly in test folder for easy run in dev environnement.

How to use bower (and/or npm) to install required test lib without have their full code in the committed project ?

Where to put test report's files ?

• in dist folder ?
• in test-out or out-test folder ?
• in test folder if test files are in a spec subfolder ?
  anywhere else ?

There are probably to many question for 1 issue but i hope most of them can be answered easily by an experienced TDD workflow user.

[sergeylukin]

That's great, I'm excited to see you moving it forward. Can't wait to start implementing it. Feel free to start prototyping though and share your progress. I will join you asap.