Yes, your tests should have the the *same *package name as your code, so in this case *package pybr*. They will not effect the package when built normally. They are only included when running *go test*. You also need to name your tests correctly, and they need a signature like:
func TestXxx(*testing.T) See the testing package documentation <https://golang.org/pkg/testing/>. - Jake On Friday, April 21, 2017 at 2:47:25 PM UTC-4, Tong Sun wrote: > > Hi, > > Thanks you all that helped. > > I choose the first option, and am now facing a new problem -- when I run > > go test -v ./... > > I got "no tests to run" even though I have a _test file: > > https://github.com/go-cc/cc-table/blob/master/cc-pinyin-range/pinyin_test.go > > For other directories, I got "no test files", which is obvious, but what > does this "no tests to run" mean and how can I fix it? > > Is it because I'm using multiple words for my project name, and I use a > different package name within it? > I've defined a type "Pinyin" in that package, so "func ExamplePinyin()" or > even "func ExamplePinyin_output()" is a good name for testing, right? > How can I make my above _test file work? > > Thanks > > > On Wednesday, April 19, 2017 at 12:18:53 PM UTC-4, Chris Manghane wrote: >> >> There's definitely no idiom here. Do what the octokittens do and probably >> use the first or second option, in that order. The third seems awkward, >> unless the underscore has some specific meaning (like how _unix is used to >> compile architecture-specific code). And I'm not really sure if the >> capitalization in the fourth actually matters. >> >> Looking at the Go repos themselves, there are examples of both: >> gofrontend and sublime-build. It seems like go-frontend and sublimebuild >> would also be reasonable names for these as well so do whatever you feel >> like I guess. >> >> Thanks, >> Chris >> >> On Wed, Apr 19, 2017 at 8:05 AM, Tong Sun <sunto...@gmail.com> wrote: >> >>> On Wed, Apr 19, 2017 at 9:59 AM, Jan Mercl <0xj...@gmail.com> wrote: >>> >>>> On Wed, Apr 19, 2017 at 3:48 PM Tong Sun <sunto...@gmail.com> wrote: >>>> >>>> > what's your preference and why? >>>> >>>> example.com/name/onenamenopunctutaionalllowercasetwotoninecharacters >>>> >>> >>> Hmm... does it meant to be sarcasm or actually recommendation? >>> Honestly, I tried to figure out the words from that long name but gave up >>> after *several* attempts. >>> >>> >>> b/c ~ what POSIX recommends for utility names. >>>> >>> >>> Any urls maybe? >>> >>> I was trying to find that myself, and found one page, >>> >>> Utility Conventions >>> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html >>> >>> Which says, >>> >>> Within POSIX.1-2008..., The utility in the example is named >>>> *utility_name*, >>> >>> >>> i.e., separated with an underscore. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "golang-nuts" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to golang-nuts...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
