Create benchmarks

[dignifiedquire]

As discussed in #110 and #95 there should be a way to benchmark testacular.
I've found this grunt task and it's really simple to setup.
But if we want to use it we need to switch to grunt@devel as this task only runs there.

Any other ideas or suggestions on how to benchmark testacular as a whole?

[vojtajina]

We really want running tests to be fast, however the node.js part of the app is more likely not gonna be the bottleneck. It's more about:

1/ how you write your js tests (as the execution time in the browser is the most significant)
2/ communication with browser (benchmarking socket.io / switching to other library)
3/ then we could benchmark memory/CPU consumption of Testacular or benchmark file resolving or bootstrapping Testacular (might be interested to compare bootstrap time after refactoring to DI)

Should we close this for now ?

[vojtajina]

Actually, I found myself running the AngularJS test suite very often (pretty much every release). Just running the whole suite for couple of times on Safari and Chrome and comparing the times, whether it does not get slower...

I think it would be a good start to automate this.

[dignifiedquire]

Closing for now, we will come back when we have time or it gets more important.