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

The "--test-recursive" does not necessarily do what people think #78

Open
zimmski opened this issue Oct 2, 2019 · 0 comments
Open

The "--test-recursive" does not necessarily do what people think #78

zimmski opened this issue Oct 2, 2019 · 0 comments

Comments

@zimmski
Copy link
Owner

zimmski commented Oct 2, 2019

If we do "go-mutesting --test-recursive some/package/..." we will go through every Go file and mutate it. The "--test-recursive" option here would maybe indicate to the user that we will run ALL test cases of "some/package". However, we only run the test cases of the package the current Go file belongs to plus all subpackages. This seems confusing and we should give a better usability for this case. Especially since one needs to add a specific exec command to test for this. What would be interesting is maybe to add a "test" (needs better wording) that represents the test command instead of being forced to write a whole exec command.

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

No branches or pull requests

1 participant