Add configuration for Testacular

[vojtajina]

$ cd <baseplate path>
$ testacular start

Note, because of https://github.com/testacular/testacular/issues/291 you need master version of Testacular, so wait for the next canary release.

[webpro]

Thanks, much appreciated!

So the issues around non-AMD scripts seem to be resolved, that looks great.

Will wait for the next canary. Guess that will (also) fix the "There is no timestamp for ..." / 404's

Any particular reason you switched to non-minified version of lodash? Just debugging I guess?

[vojtajina]

Sorry the lodash change was just leftover, I updated the pull request. For some reason there was no lodash.min.js so it didn't work for me. I didn't want to spend time debugging that, so I just used non minified lodash.

[webpro]

@vojtajina, I just tried versions 0.5.11 and 0.6 of testacular. I'm still getting a "There is no timestamp for /base/model/modelA.js!" (404) error (this is the first dependency from the first test module). It seems to not take into account the "baseUrl" setting for RequireJS. Do you think this issue should be fixed, or maybe is this another issue than https://github.com/testacular/testacular/issues/291?

[vojtajina]

That's the lodash. That's why I originally changed the lodash.min.js to lodash.js, because there is no lodash.min.js

[vojtajina]

Sorry, I misread your comment.

However, it works for me, with the latest Testacular from npm (0.6.0). I only have to change the lodash.min to lodash (in main.js).

[vojtajina]

So the problem was you renamed the directory since this PR. This works for me, but I still have to rename lodash.min to lodash, as there is no lodash.min.

[webpro]

Thanks @vojtajina! Actually my issue was that somehow I had testacular (0.5.9) also installed locally in the project (the global testacular bin uses that version). That missing lodash.min.js file is weird, I encountered it as well, but not related here.

The code coverage feature is awesome! A breeze to setup.