Go R1 Day 49

progress

• Learned about White-Box vs Black-Box testing. Apparently, you can access all indentifiers of a package if you use the same package name such as: package packagename. If you are testing as a consumer might be, then you can use package packagename_test for only accessing the exported identifiers.
• Used examples in test file to provide self-documentation of how to use the method.
• Worked further with golanglint-ci and found it challenging when working with multiple modules in subdirectories. The go eco system systems simplest with one repo = one module. While mono-repos can work, the CI tooling isn’t quite as intuitive to setup. VSCode requires experimental support for multiple modules as well at this time.

links

• Integers
• Five suggestions for setting up a Go project – The acme of foolishness
• Proper package naming for testing with the Go language - Stack Overflow
• The Go Programming Language Specification - The Go Programming Language
• chore: precommit hooks and tooling · sheldonhull/learn-go-with-tests-applied@de42a55 · GitHub
• test: ✅ integers minimal test code · sheldonhull/learn-go-with-tests-applied@37923e7 · GitHub
• test: 🎉 finish integer testing · sheldonhull/learn-go-with-tests-applied@92691f0 · GitHub