Tests are usually included in the package. Testing a package cannot become easier this way and it is the only way to test internal functions, types, variables or constants. However if you have large test files, it may make sense to keep them in a separate repository because go-getting the package would become extremely slow if included in the package.
On Wednesday, August 3, 2016 at 3:39:47 PM UTC+2, ffohw...@gmail.com wrote: > > I've got a question about best practices for test file packages, I've seen > this post > http://stackoverflow.com/questions/19998250/proper-package-naming-for-testing-in-golang > > and wanted to know if there really was a best practice for writing tests, > or if it really comes down to black/white box styles. > > > -- 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.
