Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
sainianubhav opened this issue Oct 10, 2018 · 3 comments

Comments

@sainianubhav
Copy link
Contributor

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
Copy link
Member

grawk commented Oct 11, 2018

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

@sainianubhav
Copy link
Contributor Author

How? Could you point me in the right direction?

@grawk
Copy link
Member

grawk commented Oct 29, 2018

Something like this (WIP): 4203740

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants