-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
When running an individual test it tries to run all test #21
Comments
I couldn't reproduce, I'll need to check out your repo. |
This seems to only happen when the list is collapsed. If expanding the test file to see individual tests inside the test file "Run Test" runs the test. |
Oh in that case this is a dupe of #14 if you try to run tests before "discovering" them, I just need to bolt in some logic to detect if a testfile hasn't been discovered yet and do a discovery for the adapter. |
@JustinGrote this was not fixed by #14. |
I saw it pop up "maingitbranch" there, do your tests require parameters or prompts? Interactive tests are not supported at the moment, that would be a separate enhancement. |
No, the issue is that it runs all 228 files even when I start just one. The prompt is from a test that is not part of the project that should not be shown in test explorer at all (will be fixed when issue #20 is resolved). It just happens to be that test that is the first file to run of the 228 files. |
The logic looks correct, when you click run it's passing your specific test file and line 447 as the inclusion filter. Can you take that second PesterInterface command that it runs and change the verbosity to diagnostic and psot the output? |
Not sure you have any use of the output? |
Ah didn't know that setting - learned something new. 🙂 The one "Output Verbosity" were set to "FromPreference". Changing it to |
It should default to "Normal" when it is set to "FromPreference". Seems it does not? |
Like I said probably a bug, I'll look into it and open this as a new issue. |
At least we found the issue. Thanks for the guidance! 😃 |
When choosing "Run Test" from the individual test "list" (first play symbol):
it tries to run all found tests
If choosing the second "play button" called "Debug Test" the individual test run as expected.
The text was updated successfully, but these errors were encountered: