Is there a way to know how many tests are going to run before tests start running.

[sainianubhav]

There are multiple things that can be done.

Knowing how many tests are going to run helps in gauging how much time it might take; I can plan my coffee breaks accordingly.

1. We can tell users how many tests are going to run. Just the number. This lets dev know whether the grep query accurate.
2. We call let users dry run tests, this will list all the tests that are going to run. This also helps with grep query accuracy.

I think that nemo or mocha might know which tests to run before hand, as #37 happens.

Whaddayya think?

[grawk]

I think it should be possible to ascertain # of tests to run prior to running them.

[sainianubhav]

How? Could you point me in the right direction?

[grawk]

Something like this (WIP): https://github.com/krakenjs/nemo/commit/4203740f5d00e828ef73f93ec51c711222d772e1