-
Notifications
You must be signed in to change notification settings - Fork 345
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
How to generate named tests? #177
Comments
OK, seems that the code that implements |
Well you can just pick dev branch, it’s actually stable. At least it was 9
month ago. @cweill is/was pretty busy at that moment to release changes
from develop branch.
…On Fri, 4 Nov 2022 at 16:20, Juris ***@***.***> wrote:
OK, seems that the code that implements -named functionality has not been
released, meaning it is still in develop branch.
@cweill <https://github.com/cweill> Can we expect v1.7.0 release at some
point? 🙏 Otherwise go install ...***@***.*** pulls in v1.6.0.
—
Reply to this email directly, view it on GitHub
<#177 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE7EMBUZNWF5QLYRIQBFFLWGULTFANCNFSM6AAAAAARXGKTIY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@butuzov Yes that is one way, just have to remember when updating all Go tools from VS Code Go extension that I need to manually update |
If you specify path to go tests located elsewhere, viscose updating to @latest wouldn't affect your setup. It's possible with vscode extension. |
This is still causing an issue, any info when a version with -named will be released? |
@cweill good question. Charles, can we have it? |
Would be great, any updates on this? |
Hi,
How to generate named tests using map instead of slice? Doing a bit of archeology there seems to be support for this as part of #148. But how one can enable it from commandline? I cannot find any examples, or help or reference information. Passing
-named
does not work.Would be great to add some help with examples?
gotests v1.6.0
cc @butuzov
The text was updated successfully, but these errors were encountered: