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

Jump to bottom

testing: Test-case name convention #30599

Closed
cn007b opened this issue Mar 5, 2019 · 2 comments
Closed

testing: Test-case name convention #30599

cn007b opened this issue Mar 5, 2019 · 2 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@cn007b
Copy link
Contributor

cn007b commented Mar 5, 2019 •
edited

Does it make sense to have some kind of convention to name test-cases like this: Test_{StructName}_{MethodName} for struct's methods and Test_{FuncName} for regular functions, so now it's simple to figure out method/function and navigate this test-case through project.
@mvdan
Copy link
Member

mvdan commented Mar 5, 2019

Are you asking a question? If so, see https://github.com/golang/go/wiki/Questions.

If you're suggesting a documentation change somewhere, please clarify what you're proposing.

@cn007b cn007b closed this as completed Mar 6, 2019
@cn007b cn007b reopened this Mar 6, 2019
@ianlancetaylor ianlancetaylor added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Mar 6, 2019
@gopherbot
Copy link

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@golang golang locked and limited conversation to collaborators Apr 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ianlancetaylor @mvdan @cn007b @gopherbot