Removing docs task from test, test-browserify and coverage build chain

[paolodm]

As mentioned in #799, an extra directory is being created upon grunt test. This directory, web/docs/public, is being created as part of the grunt-docco2 task.

It seems misplaced to me to have to build the docs during a test run. I don't think a user running grunt test expects the docs to be built during this phase of the build lifecycle. IMO, an appropriate place to build the docs is during the grunt build task.

[gordonwoodhull]

Thanks.

The problem with this is that if you don't do the build when you run the tests, you can't be certain that you are running the tests against all the latest changes (when doing development).

However, I think we can do something similar where the core artifacts are built but not the documentation.

[paolodm]

Are the docs a prerequisite to running the tests? If they are, then I agree that you need to fire the docs task for the tests.

[gordonwoodhull]

No, I'm just saying that the tests do depend on the file dc.js being built. I'm going to go with a simpler change with the same goal. Thanks for bringing this up.