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

differing number of tests #70

Open
silent-e opened this Issue Nov 23, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@silent-e

silent-e commented Nov 23, 2017

I've just encountered an interesting issue. I have a suite of Minitest tests. When running bundle exec m and running bundle exec m -r test I am seeing a different number of tests being run. The difference appears to be the number of tests that aren't in the standard set of test folders.

I have a test/services folder where those tests aren't running during the bundle exec m run but are in the recursive call. Also, The tests are running when I specifically run bundle exec m test/services/[test file name] so I know the m gem is picking them up at some point.

Thoughts?

(e)

PS: be in my screenshots is just my alias for bundle exec

screen shot 2017-11-23 at 4 56 43 pm

screen shot 2017-11-23 at 4 56 55 pm

@zamith

This comment has been minimized.

Show comment
Hide comment
@zamith

zamith Dec 14, 2017

Collaborator

That is odd and should not be the expected behaviour. I'll look into it. Thanks.

Collaborator

zamith commented Dec 14, 2017

That is odd and should not be the expected behaviour. I'll look into it. Thanks.

@silent-e

This comment has been minimized.

Show comment
Hide comment
@silent-e

silent-e Feb 24, 2018

followup… In parser.rb you are calling rake test if no argv is passed in. According to what I've read rake test does not attempt to run tests outside the standard set. But rake test:all does.

Perhaps changing to calling out to rake test:all is the better solution.

Just a thought.

(e)

silent-e commented Feb 24, 2018

followup… In parser.rb you are calling rake test if no argv is passed in. According to what I've read rake test does not attempt to run tests outside the standard set. But rake test:all does.

Perhaps changing to calling out to rake test:all is the better solution.

Just a thought.

(e)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment